Move to completed, keep seeding

[m1dnight]

Hi,

I'm using Transmission in combination with an automatic unrar program. This program requires my torrents to be moved to the \completed\ folder.

I download my torrents to \Transmission\incomplete, and when they are finished (ratio reached AND torrent fully downloaded, I suppose?) they are moved to \Transmission\complete

Now I've downloaded a few things, and they don't appear to be move to the completed folder. I can't seem to figure out what the exact criteria are to be moved.

I have a movie that was moved to the completed directory right after it had finished downloading, without any seeding. Some torrents completed downloading but haven't been moved to the completed directory.

This is my settingsfile: http://pastebin.com/Zhk33AyY

Any help is greatly appreciated,

[m1dnight]

Okay, this is what I did:

Transmission was already running.
I executed: "transmission-daemon --logfile /etc/transmission-damon/log.log"
I added a new torrent to see if it would generate some log entry if completed
It didnt do anything, didn't move the torrent either.

I suppose that while transmission is already running executing "transmission-daemon --logfile..." sends this to the running process, and does NOT start a new one? Or am I wrong here?

I tried stopping the service. Then I executed said command but this made my transmission web interface give a 503.


It appears that running transmission this way:
"sudo service transmission-daemon start" runs transmission with the config located in "/etc/transmission-daemon"
Running it by executing "transmission-daemon --logfile .." runs transmission using the config file in "/home/<username>/.config/transmission-daemon"

Okay, so I've been looking around a bit and I'm very confused now

What is the difference between the program "service transmission-daemon start" and "transmission-daemon" ?

They seem to be two different programs. I started out with the first one, and added 4 torrents. After a reboot I seem to automatically start the first one as well.

I think I need to configure some more. But I'm stuck..

I'm a bit confused here now..

[blacke4dawn]

I suppose that while transmission is already running executing "transmission-daemon --logfile..." sends this to the running process, and does NOT start a new one? Or am I wrong here?

Yes, you are wrong. Running it again in that way starts a new instance of the daemon, so you end up with two of them running. Any options that you can change while the daemon is running can be changed via transmission-remote tool or essentially any graphical UI that connects to that daemon. If you can't change what you need through those then the changes needs to be applied via editing the proper files and a restart of the daemon.

What is the difference between the program "service transmission-daemon start" and "transmission-daemon" ?

The first one is a start script/routine that has presets determined by your distribution maintainer while the second uses the hard-coded defaults set by the devs. They are still the same program just with different start options supplied.

[m1dnight]

Excellent I understand it now. I cleared my settings (actually reverted to an old snapshot of my VM) and just set it up and ran it via the service. All works without any issues now. Thanks for the explanation! I'm a huge linux noob who's grateful!