Pulver: Yes, of course. I also checked with 'netstat -tlnp' that rtorrent is actually listening on that port.
A remote interface can be useful, especially a Web interface, in some circumstances. But it may never be as complete and easy to use as rtorrent itself. And there are multiple advantages to rtorrent running in screen over ssh: the connection will only eat up a few KB/s, it will respond promptly, it won't need additional resources over what rtorent already consumes and so on.
I'll admit at some point I was loving transmission and didn't like the idea of rtorrent, but nowadays I'm surprised to see I've changed my mind completely.
al: edit /usr/local/sbin/pre-shutdown, put this in it:Make sure pre-shutdown is executable.Code:#!/bin/sh /bin/kill -INT $(/bin/pidof rtorrent)
Also, you need to set a session directory (session = dir) in rtorrent.rc, rehash all the torrents at least once, and restart rtorrent, for the data to enter the session files.
But to be frank I've had mixed results so far. If I kill -INT rtorrent from the command line it works as expected, when I restart it the hash will jump to 100% and download will resume immediately. But it doesn't work like that with pre-shutdown. I believe rtorrent needs a few seconds to actually dump the session data, and the router reboots before that. So try this intead (untested yet):
Try with bigger sleep intervals as well, although I read somewhere that about 5 seconds should be enough for rtorrent to do its thing.Code:#!/bin/sh /bin/kill -INT $(/bin/pidof rtorrent) & /bin/sleep 10
Of course, remember to do 'flashfs save && flashfs commit' to save pre-shutdown to flash!
The idea is that when I modify something in the config and need to restart the router I shouldn't have to rehash anything in rtorrent, just resume smoothly where it left off.




Reply With Quote