NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Transmission mistake in start.sh and settings.json question
Hi all, Not sure if I made this mistake and now it's propegating or it is actually a mistake in the Transmission source for Readynas (which I don't where to look for it). In the start.sh file...
Have tracked it down and here is the issue:
The config file re-writes itself if there is an entry in a format it doesn't like, even though the command line may accept the format.
Some entires in the config files accept wildcards (*), some accept comma deliniated entries such as the rpc whitelist address, some do not. So an IP on the whitelist to allow 192.168.*.* works fine, entering it in the same format for another entry may or may not work. The documentation is sparse on this but it can be found pouring through source.
Furthermore, the command line daemon entires accept for example: 10.0.0.0/8 and actually function with such entires for certain parameters but the config file does not.
Best bet if you want to get fancy, start the entire thing from command line with the exact arguements you want and to heck with the config file OR figure out the exact syntax accepted by the config file. The random ports and others can actually be more than one entry via command line but cannot via the config file. The config file WILL rewrite itself over a bad entry (kinda cool, kinda not) so it keeps n00bs like me from doing dumb things and the process just failing to start and throwing an error in the front-end interface.
Problem solved.
Stop transmission before making a change in settings.json then you change should stay
Thank you for the reply super_poussin but unfortunately that is not the case (Although some documentation tells you it should be).
The file in /data/Transmission/config/ re-writes on start (even when the daemon is not running) AND on close. Not sure why that is. So even if the daemon is not running, the changes do not stay. I can literally watch the file re-write itself from tmp. Its totally crazy. The settings must be stored some place but where I have no idea!!!
Thus my problem :)
Do you know of an alternate location where the config file might be stored and actually accept changes?
To add some more information:
Running transmission-daemon from the command line does NOT re-write the config files. The act of "Flipping the switch" in the GUI does. On or Off it doesn't matter, flipping that switch causes the config files to overwrite.
Have tracked it down and here is the issue:
The config file re-writes itself if there is an entry in a format it doesn't like, even though the command line may accept the format.
Some entires in the config files accept wildcards (*), some accept comma deliniated entries such as the rpc whitelist address, some do not. So an IP on the whitelist to allow 192.168.*.* works fine, entering it in the same format for another entry may or may not work. The documentation is sparse on this but it can be found pouring through source.
Furthermore, the command line daemon entires accept for example: 10.0.0.0/8 and actually function with such entires for certain parameters but the config file does not.
Best bet if you want to get fancy, start the entire thing from command line with the exact arguements you want and to heck with the config file OR figure out the exact syntax accepted by the config file. The random ports and others can actually be more than one entry via command line but cannot via the config file. The config file WILL rewrite itself over a bad entry (kinda cool, kinda not) so it keeps n00bs like me from doing dumb things and the process just failing to start and throwing an error in the front-end interface.
Problem solved.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
