Transmission

It logs to /var/log/messages

yes i previously had checked there and /var/log/syslog , and just now tried changing permissions to 666 but still nothing is showing up in those logs. as you mentioned this works..

TR_DEBUG_FD=1 transmission-qt >./qt.log

but the logfile contains far too much detail ...

I just built transmission-qt version 2.50 in debian, but i cannot figure out how to view or specify a logfile. The message-level is set to 3 in settings.json. There is nothing in the manual or --help regarding logs, nor anything in the GUI that i could find.

Otherwise everything works great.

you're right there is no ./configure switch, instead build normally then descend to qt directory and follow the README.txt


qt/README.txt

BUILDING ON UNIX

1. Prerequisites: Qt >= 4.6 and its development packages
2. Build Transmission as normal
3. In the qt/ directory, type "qmake qtr.pro" or ...

hopefully they can add the feature to run script on torrent add that would be optimal for this script!

i don't see why you need that, if you run script as a cron job it will check automatically (say every 5 minutes) and turn on dht and pex when it recognizes that activeTorrentCount is not 0 ...

sintek, this script cron-transmission.sh will check activeTorrentCount and turn off dht and pex when equal 0, and turn them on when not. I ran manually and it works fine for me. the idea would be to add it to cron and check every 10 minutes, for example, torrents status. everything will now be ...

if you don't need some fancy GUI button, this can already be accomplished in terminal very easily with transmission-remote command:


$ transmission-remote -t all --stop ; sleep 15m ; transmission-remote -t all --start


the above pauses all torrents, waits 15 minutes, then starts them up again ...

it doesn't look like your script ever writes the changes to the file, it just gives screen output. maybe try this instead..


cat $user_conf # echo file before change

read password
sed -i -e "s/.*rpc-password.*/ \"rpc-password\": \"$password\",/" $user_conf

cat $user_conf # echo file after change ...

After the next scrape or announce (I'm not sure which corresponds to peers, and which to "peer counts") everything is back to normal.

i generally run only the daemon (not gtk or qt) and always with latest version (now at 2.50) . using the terminal-based interface transmission-remote-cli.py i get ...

What's wrong with the first picture?

The tracker seems to be responding, but there is no detail on the number of seeders and leechers, ..

I wonder in that first case if announce worked, but the scrape failed, which might explain the lack of seeder and peer count. I've seen that happen on my end ...

I bought the DNS-320 NAS a few days ago and installed transmission and transmission remote gui on it through these guides :

that seems odd, shouldn't transmission-remote-gui be installed on the the remote device, not on the NAS itself?

FYI, I forwarded ports 51413 and 9091 (TCP and UDP) to 192 ...

I didnot open/close any ports. I just checked if daemon was running (sysctl status transmission-daemon.service) which it was. Then I ran the script. Which did nothing. I checked Transmission-gtk and my torrents were stuck! There were no peers...they were just stuck. When I removed the daemon and ...

it looks like your ./configure worked OK, but reading your post you left out the 'make' part. building is usually three basic steps:

./configure
make
make install

in that order.

Snupple wrote:You mean this?

yes, it looks like the announce of the second tracker in your screenshot failed, which is not uncommon these days.

Man, It doesn't work even while watching directory.

Check it over plz.

OK i checked it again, and it does work perfect for me also for torrents added in watch directory, using transmission-daemon 2.42+ (13218) . And it's documented in my logfile..


Watching "/home/user1/btornado/tmp/" for new ...

see https://trac.transmissionbt.com/wiki/EditConfigFiles#Misc

in settings.json:

script-torrent-done-enabled: Boolean (default = false) Run a script at torrent completion (set to true)
script-torrent-done-filename: String (default = "") Path to script (self-explanatory)

this is very simple test ...