Transmission

YAY!!! Got it to work!

In /etc/init.d/transmission-daemon file I found that there was as DAEMON-SETTINGS variable what was forcing some settings and this is why some setting would change and not others. So this sorted the settings.json overwriting issue.

I then found that even with the settings ...

Thanks for the reply.

I have already left a comment on the CentOS package maintainers blog http://geekery.blog.com. Hopefully he will pick this up and take a look.

I cannot use the GUI as my server does not use one. So I have no option but to use the settings.json file. transmission-daemon is ...

Also making the file read only does not work. Transmission changes the permissions back to 600 automatically and then overwrites the file.

If anyone knows how to stop this from happening. Then please let the package maintainer know and they should be able to resolve

I would think that this is CentOS specific as im having the same issue with CentOS 6 however. I would of thought it would be up to a transmission developer to try to work this out and either patch it or make the rpm maintainer aware so they can fix it.

The only way I know currently is to stop the transmission-daemon make your changes and start it again. But this doesn't always work

/Rant

Why is is everytime I need to install transmission the simple job of editing the settings.json file turns out to take hours of my time?

firstly I stop transmission-daemon so its not running make my edits start it again and it overwrites the settings.
I somehow managed to make some edits and ...

No it does not.

Hello All,

I have moved to fedora 17 recently and have setup Transmission-daemon on it which went very smooth. I even wrote a little how-to guide...go me :)
http://danielgibbs.co.uk/2012/06/fedora-17-install-transmission-headless-server-with-web-interface/

I have installed Remote Transmission ...

Just an update. I found this script while searching (I cannot remember the site I got it from. If you know please post below)


#!/bin/bash

# blocklist directory
BLOCKLISTDIR=/var/lib/transmission-daemon/info/blocklists

cd ${BLOCKLISTDIR}
if [ $? -eq 0 ]; then
if [ -f level1 ]; then
rm level1 ...

O nice thanks. I will give this a try tomorrow and let you know how I get on. I did find a script that should do what you did automaticly. So I will have a play with that as well. I guess this feature wont work on Debian until they update the repository or compile from source.

Looks like the file im editing is a symbolic link to that file. They are both matching and are the same

root@tracker.example.com:~# ls -al /var/lib/transmission-daemon/info/settings.json
lrwxrwxrwx 1 root root 38 Jul 9 19:53 /var/lib/transmission-daemon/info/settings.json -> /etc/transmission ...

root@tracker.example.com:~# dpkg -l|grep transmission
ii transmission 2.03-2 lightweight BitTorrent client
ii transmission-cli 2.03-2 lightweight BitTorrent client (command line interface)
ii transmission-common 2.03-2 lightweight BitTorrent client (common files)
ii transmission-daemon 2.03-2 ...

I have tried this but still the same error.

Here is exactly what I have typed

root@tracker.example.com:/# /etc/init.d/transmission-daemon stop
Stopping bittorrent daemon: transmission-daemon.
root@tracker.example.com:/# killall transmission-daemon
transmission-daemon: no process found
root ...

Thanks. However I had already set the blocklist up which this configuration. I tried it again anyway however still got the same error.

root@tracker.example.com:/var/lib/transmission-daemon/info# transmission-remote --blocklist-update
localhost:9091 responded: "http error 404: Not Found"

the ...

Hello All,

As a project on the weekend I am trying to setup a headless transmission server on Debian with automated blocklist updating.

I am doing this to replace my Win 7 utorrent + peerblock setup which is not as streamlined as I like. After doing a bit of research Transmission seems to be the ...