Transmission

I had this same problem a long time ago where my Watch folder and Torrent folder were the same. Try making them different folders.

Can anyone else confirm this bug on the nightlies? I'd really like to know if it's something unique to my setup.

I think I found the problem, now whenever a .torrent files is added, it is immediately renamed to "filename.torrent.added" and it appears that the watch directory doesn't automatically add .added files on restart.

I verified this by stopping transmission-daemon, renaming the .added files to ...

Starting with the nightlies a few weeks ago (sorry I can't be more specific), transmission-daemon no longer remembers what it was doing before it was restarted. If I manually re-add the torrent files it picks up right where it left off. I'm assuming this means that the resume files are intact and ...

I solved my own problem and thought I'd share if anyone cares. I decided to try to manually start the daemon without the "--background" switch to see if any error messages were popping up that I wasn't seeing though other methods. So I ran:


start-stop-daemon --chuid "transmission" --start ...

I've been keeping pretty up to date with the Nightlies and started having trouble with the daemon shutting down randomly starting about Saturday 4/24. Today I was running 10533 and was experiencing the problem that was fixed in 10534. Ever since that update, trying to start the daemon from the init ...

So I played around with the start-stop-daemon but couldn't get it to work without KILL. I decided to write a script to pause all, restart Transmission, resume all. I then run this as a cron job.

There is one issue that came up, torrents that have finished seeding will resume with the ...-tall -s ...

The restart command I'm using comes from the init.d script and is as follows:
Is there a better way to implement this?

Data verification happens on all active downloads when the daemon restarts. Is that not how it's supposed to work?

I'm running transmission-daemon and I'm trying to set up a cron job to automatically update the blocklist. When I run the job:

@midnight /usr/local/bin/transmission-remote --blocklist-update
I see that the blocklist file gets updated as expected. The only thing that I'm wondering is if, after the ...

So I fixed this by making a symbolic link to the torrent and resume folders out to my External. Now the .torrents from the WebUI are saved and .resume files are created. Wahoooo!

Having an issue getting transmission-remote-cli working. I installed the required packages from http://github.com/fagga/transmission-remote-cli and created a config file, but now every time I run it I get this error:

YahiSheeva:/usr/local/bin# transmission-remote-cli.py
Traceback (most recent call ...

I'm having the same problem running 1.82 on a SheevaPlug with a headless Debian Squeeze build. The specific symptom that I am seeing is that whenever adding a torrent by URL (either in the WebUI or through transmission-remote) the .torrent file never gets saved anywhere. Also, when I restart the ...