It doesn't save the Remote Preferences

[GoogleCodeExporter]

transmission-remote-gtk svn version
Transmission 3.41
Ubuntu Natty 64 bits

I have incremented from 3 to 4 the global share ratio in Remote Preferences.
Apparently it saves this setting but, after the server is rebooted, the global 
share ratio is 3 again. 

Original issue reported on code.google.com by si...@simonbcn.net on 19 Oct 2011 at 11:33

[GoogleCodeExporter]

Are you using the latest SVN? I fixed the display issue you reported and it now 
seems to work fine for me, I just tried it.

If it's not being saved across a reboot I would think that's Transmission not 
saving it. The reason is, if you save a setting, then open remote preferences 
again and see the right value, that's come from the latest session-get response 
from the server (done automatically after the session-set). If you can see it 
there, I think it's unlikely to be a trg issue.

Can you confirm it is shown when you go into remote preferences after?

Original comment by a...@eth0.org.uk on 20 Oct 2011 at 7:41

[GoogleCodeExporter]

transmission-remote-gtk svn version rev. 303 (compiled now).

I change the "Seed ratio limit" from 3 to 4 in "Remote preferences". I confirm 
the change pressing "Accept" button (I attach one screen-shot).
I open again "Remote preferences" and it shows "Seed ratio limit"=4. It's 
correct.
But in settings.json (in server) it still shows the old value:

$ grep ratio .config/transmission-daemon/settings.json 
    "ratio-limit": 3, 
    "ratio-limit-enabled": true,

When I restart the server, the value of "Seed ratio limit" is again the value 
in settings.json, 3 and not 4.

The modifications done with transmission-remote-gtk aren't permanents.

Original comment by si...@simonbcn.net on 20 Oct 2011 at 2:48

Attachments:

• captura_1020_16:46:36.png

[GoogleCodeExporter]

A Transmission RPC client like transmission-remote-gtk can only do what the RPC 
interface allows it to, and the RPC doesn't have a concept of making a setting 
permanent or not, saving settings to disk.

In this case, all it can do is send a session-set request with the correct 
parameters. As I mentioned, this dialog displays the latest session-get 
response, so if you see the correct setting means that transmission-daemon has 
accepted your setting and has it in memory.

I don't know how Transmission handles saving settings, but it's quite likely it 
does it during a graceful shutdown, not immediately. I'd suggest you try doing 
a 'clean' shutdown of Transmission, if you aren't already, using SIGTERM and 
not SIGKILL. Or maybe this one setting is missing from the save code, I'm not 
sure.

So there's not much I can do here on my end, you need to figure out why 
Transmission isn't persisting the setting. If you want to check it really is 
going out in session-set and back in session-get you can ./configure with 
--enable-debug and start with TRG_SHOW_INCOMING=1

https://trac.transmissionbt.com/browser/trunk/extras/rpc-spec.txt

Original comment by a...@eth0.org.uk on 20 Oct 2011 at 3:11

[GoogleCodeExporter]

I've stopped the transmission-daemon in server (with 
"/etc/init.d/transmission-daemon stop") and it has saved this setting. ¿?
Perhaps the shutdown process, in the server, doesn't wait for 
transmission-daemon stops completely.

Original comment by si...@simonbcn.net on 20 Oct 2011 at 3:18

[GoogleCodeExporter]

:)

Original comment by a...@eth0.org.uk on 20 Oct 2011 at 3:21

• Changed state: Invalid