Transmission

Ortix, if the script normally takes a long time to finish, try doing this:
and see if it makes a difference.

first you have to enable the script-done feature in settings.json:

"script-torrent-done-enabled": true,
"script-torrent-done-filename": "/path/to/your/uploadscript",

then make sure script is executable "chmod 755 uploadscript"

the actual uploadscript might look someting like this:


#!/bin/bash ...

yes that wiki link is for Debian/Ubuntu startup scripts .. yours is a different animal.

I got the tar ball from the following support link:

http://www.embeded-systems.net/software.htm under the transmission selection window, it says its version 1.72 when I download it...

i grabbed that tarball ...

you have to stop the transmission-daemon from running before editing settings.json or the changes won't stick.

also at any time you can run command:

transmission-daemon -g config_dir --dump-settings

to see what the current settings really are. just curious, do you use something like telnet or ssh ...

How about adding TR_DOWNLOADED_PATH variable with the full path to the finished downloaded file or folder?

isn't that in effect already included in the present env variables TR_TORRENT_DIR and TR_TORRENT_NAME


TR_DOWNLOADED_PATH="$TR_TORRENT_DIR/$TR_TORRENT_NAME"

or maybe things are different ...

you seem to have left out the "shebang" line (the interpreter the script is to run under). try this:


#!/bin/bash
echo "haha !!!" >> /tmp/test.test
echo "Un torrent est termine de se telecharger : http://mydomain/downloads" | mail -s "Torrent termine" myself@gmail.com

i'm assuming you're running Lenny and there is no transmission-daemon package. in fact all the Tranmission packages available in Lenny are ancient and out-dated. one solution is to use lenny-backports:

http://backports.debian.org/Instructions/

and then do "apt-get -t lenny-backports install ...

i wonder if this has something to do with this bug:

https://trac.transmissionbt.com/ticket/3453

which was fixed in the TR 2.10 release.

kill -TERM <daemon's pid> shutdown normally. but sometimes cause some unfinished torrents to force verify.

i've found that if you do a

transmission-remote -t all --stop

right before the "kill -TERM <transmission-daemon's pid>" command you can avoid unexpected force verifies. at least that's my ...

I've installed transmission on Debian Lenny headless..

doing "apt-get install" in a pure Lenny system will bring in TR 1.22 .. a really ancient and dated version. i don't think it even uses a settings.json file.

you could consider installing from lenny-backports and getting TR 1.77, which does ...

that wiki page is probably out of date since it was written when libevent was included in the transmission source package, but it isn't in now. it happened to me also running Debian, and solution was to:

apt-get install libevent-dev

which brings in version 1.4, older versions won't work. i googled ...

The bottom of my man page says "July 21, 2008" Am I out of date?

this is "transmission-remote --help" from transmission-remote 2.11+


transmission-remote 2.11+ (11356)
A fast and easy BitTorrent client
http://www.transmissionbt.com/

Usage: transmission-remote [host] [options]
transmission ...

you have to close down Transmission before editing settings.json otherwise the changes won't stick.

erins2 wrote:Is there now a way to set per-torrent limits using transmission-remote?

yes that's been in recent versions for some time now.

transmission-remote -t <ID> -d 75
transmission-remote -t <ID> -u 20

for setting individual torrent down and up speed limits in KiB/s

if [ -e "$PATH" ]; then
if [ -d "$PATH" ] ; then
$RSYNC -ruv $PATH $DHOST >> $RSC 2>> $ERR &
else
$RSYNC -uv $PATH $DHOST >> $RSC 2>> $ERR &
fi;
fi;



first thing, you should always put quotes "" around the dir/file paths in your scripts as torrent names often have spaces and/or non ...