I'm after some help with Transmission on my Seagate Personal Cloud Nas.
The Nas has Transmission installed out of the box, but has a front end that's not very configurable (can only set down/up limits), but it also sets the configuration file so that I can't seem to edit Transmissions settings.json and make the settings stick.
I know that Transmission must be stopped for settings to stick, so I use (logged in as [root@PersonalCloud ~])
It responds with
localhost:9091/transmission/rpc/ responded: "success"
but then respawns when checking with
ps -A | grep transmission
8139 root 0:00 /usr/bin/transmission-daemon -f --config-dir /lacie/torrent_dir/transmission --pid-file /var/run/transmission.pid
so the front end/Nas software must be controlling it.
If I do a kill (Transmission process ID), it dies, but when I write to settings.json (located in /lacie/torrent_dir/transmission), and confirmed by going back into the file after writing, the settings get overwritten when I restart it through the webbrowser controller.
Does anyone have any pointers on how i can get the settings to stick? This external post on the transmissionbt forums – clickymentions an init script that is passed to the daemon – but I have very little linux experience, and don't know how to progress.
Is there a way in Linux to see what has called a process?
Any help is appreciated.
I didn't find the right solution from the internet.
http://forums.whirlpool.net.au/forum-re ... ?t=2631988
Installation of the Miditzer on Linux machines
1 post • Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest