Transmission

Ummmrmmm.. yeah, that did it. Actually, I ran `transmission-remote -asc`. Thanks!

Actually that was pretty obvious both in the settings file and in the output of `transmission-remote -h`. I'm not sure how I missed it, except maybe if it was changed from previous versions and I hadn't reread them in ...

Is there a way to get transmission-daemon to update (write) its settings file?

I've set the alternate speed to end at 0800, but it's still running after that time.


$ date
Wed Apr 27 14:31:44 ADT 2011

$ head ~/.config/transmission-daemon/settings.json
{
"alt-speed-down": 100,
"alt-speed-enabled": true,
"alt-speed-time-begin": 1,
"alt-speed-time-day": 127,
"alt ...

Okay. Should I submit a bug report on the documentation? Or is this obvious to most people?

Okay, this seems to work. My new script:


#!/bin/bash
TORRENT_DIR=~/Downloads/torrents/%queue;
ADDED_DIR="$TORRENT_DIR/%added";

TRANSMISSION_REMOTE=/usr/bin/transmission-remote;

LOG_FILE=~/var/log/transmission-daemon/add-least-recent.log;

# Do everything in a subshell.
# This is needed under ...

Looks like that's it — I'm running 2.05, still the current version in ubuntu 10.10. Thanks for the tip. I guess I can work around it by firing the action in a subshell.

I'm able to use the --torrent-done-script option to specify a script to run when a torrent completes.

I'm using a bash script, and calling exec >> logfile so that it will log its output.

It is supposed to add the oldest of the .torrent files in a queue directory.

However, when it runs, I just get ...

Okay, thanks. Are you also saying that it doesn't also have a per-torrent mode? Some of the options, like for example `-d`, can be used both as global options and to control per-torrent behaviour. It would make sense semantically for `--torrent-done-script` to work this way.

It's not clear from the limited documentation whether the `--torrent-done-script` option to `transmission-remote` works globally, in a way specific to a particular torrent or torrents, or whether it can be applied in either of these fashions. There's no indication from either `transmission-remote ...

Just a note: It looks like it's getting the user wrong, too; on my machine, running 1.75 under Ubuntu Intrepid, it's looking under the home directory of the currently-logged-in user, rather than the non-existent home directory of the debian-transmission user. Well, at least that's what the error ...