Thread: rtorrent experts needed; moving finished downloads, but continuing seeding...

I'm looking for some expert level advise on how to get rtorrent to move finished downloads into a "finished download" directory, yet keep seeding them.

So we're clearly going to need to schedule tasks within rtorrent, and it's simple enough to cue off of a torrent state change (in this case "on_finished"). How exactly do you get finished torrents moved over? Can the command called by the scheduled task be any os command, or must it be an internal rtorrent command? And how can we point the torrent to the download's new location to keep it seeding?

I'm hoping that much of this can be done from within rtorrent, by configuring the .rtorrent.rc file. I can see how this process can be helped with external scheduled shell commands, but I'm hoping that someone's figured out how to hack together this functionality before I start re-inventing the wheel.



Thanks for any help

Yes this can be done with the rtorrent.rc file. All u need to do is add a line, like this, to the config file:

system.method.set_key = event.download.finished,move_complete,"execute=mv,-u,$d.get_base_path=,/path/to/new/dir;d.set_directory=$/path/to/new/dir"

Make sure its all one line or rtorrent wont be able to read it. Also if u use rutorrent there is a plugin called auto_move which takes advantage of this without adding any line to the rtorrent.rc file. i never used it before, but u may want to check it out.

Originally Posted by MikeD

Yes this can be done with the rtorrent.rc file. All u need to do is add a line, like this, to the config file:

system.method.set_key = event.download.finished,move_complete,"execute=mv,-u,$d.get_base_path=,/path/to/new/dir;d.set_directory=$/path/to/new/dir"

Make sure its all one line or rtorrent wont be able to read it. Also if u use rutorrent there is a plugin called auto_move which takes advantage of this without adding any line to the rtorrent.rc file. i never used it before, but u may want to check it out.

Thanks Mike, if only I knew what to look for. This call to "system.method" isn't documented in the manual pages, horrible.