Menu

#334 Settings.json not saving option about queue

New
nobody
None
Medium
Defect
2012-11-18
2012-11-15
Anonymous
No

Originally created by: Matheus....@gmail.com

What steps will reproduce the problem?
1. Stop Transmission service 2.60-1 on SNAKE OS V1.3.2 (20111019)
2. Open settings.json file that is inside .config\transmission-daemon
3. Edit the line "download-queue-size": 5 to "download-queue-size": 1
4. Save.
5. Start the service again.

What is the expected output? What do you see instead?

I expected the file with the edit but it became 5 again. The changed value do not save.

Discussion

  • Anonymous

    Anonymous - 2012-11-16

    Originally posted by: Matheus....@gmail.com

    Now, I am trying to do this:

    In other words, this is the procedure, entirely in a SSH session:

    1 - Stop transmission ( /etc/init.d/transmission stop )
    2 - Edit the file /etc/default/settings.json (Don't change the paths...)
    3 - Start transmission ( /etc/init.d/transmission start )
    4 - Save the NAS config ( /usr/share/snake/config save )

    But get a warning like Permission denied in step 2.

    using ext3 here

     
  • Anonymous

    Anonymous - 2012-11-16

    Originally posted by: stefansc...@googlemail.com

    Try editing /opt/etc/config/transmission.json. The transmission related files under /etc/ are leftovers from older versions.

     
  • Anonymous

    Anonymous - 2012-11-16

    Originally posted by: stefansc...@googlemail.com

    You should use "/opt/etc/init.d/transmission stop" to stop transmission.

    You'd have to use vi if you want to edit the file with putty. It's not the most pleasant text editor though..

    The steps would be:
    /opt/etc/init.d/transmission stop
    vi /opt/etc/config/transmission.json
    /opt/etc/init.d/transmission start

    using vi:
    hit "i" to enable edit mode
    make your changes
    hit ESC and enter ":wq" to save and quit

    Alternatively you may be able to access the file via windows explorer too. If you share the whole disk it should be at .optware/etc/config/transmission.json.

     
  • Anonymous

    Anonymous - 2012-11-16

    Originally posted by: Matheus....@gmail.com

    Ahhh, ok. Thanks. I get the point how to use the command vi. It open the file so I can edit it. I tested it here.

    BUT, the file I am tying to edit is not the transmission.json. Is the settings.json.

    That is because the file transmission.json do not have the line:

    "download-queue-size": 5

    only settings.json has it.

    And, sure. I opened it from explorer but the changes do not still after service start.

    bye

     
  • Anonymous

    Anonymous - 2012-11-17

    Originally posted by: stefansc...@googlemail.com

    Add the missing entry to transmission.json then. It comes from an older version of transmission that didn't have it yet.

    You could also make your changes in setting.json then overwrite transmission.json with it.

     
  • Anonymous

    Anonymous - 2012-11-17

    Originally posted by: Matheus....@gmail.com

    Nice, man!!!

    I am back to say my experience. Maybe someone will see this topic and can help.

    Well, I do not know why but your advice was not working. So I unistalled transmission, installed it again and made the changes in windows explorer on transmission.json file.

    I added two lines in transmission.json:

    "download-queue-enabled":true,
    "download-queue-size":1,

    Saved and restarted transmission. Now it is working like a charme!!!!

    One thing that I found is that using transmission remote gui is really nice. To control the torrents is much easier.

    Thanks for you help again.

    I have just another question, but this one is not so important.

    Well, i using transmision remote gui like a said before. I can now queue all torrents. BUT when I stop the service and start it again, the queue from before is not valid any more.

    The service put in an order that I do not configured. So, tit is not saving the order of the queue.

    Not a big problem, but if it has a solution.....

    Advice to next update for transmission: make it easier to config the queue. This gave me a bad headaque.

    bye

     
  • Anonymous

    Anonymous - 2012-11-18

    Originally posted by: stefansc...@googlemail.com

    I could add those options to the transmission settings. Or add an option that stops snake from overwriting settings.json. The way it works right now makes sure that getting transmission back into a sane state is just a restart away though.

    You shouldn't need "download-queue-enabled" btw. It's enabled by default.

    There seems to be a ticket in the transmission bug tracker about that queue reordering thing.. so hopefully it will be fixed eventually.
    https://trac.transmissionbt.com/ticket/4540

     

Log in to post a comment.

MongoDB Logo MongoDB