![]() ![]() torrent file and the listing from Deluge, not the data). The first one grabs the cookie and the second one asks Deluge to remove the torrent that just completed (only the. So what seems to be happening is that the Execute plugin successfully executes the script every time (as the Perl script needs the Execute arguments to move the torrent into rTorrent), but then the problem arises with the curl commands. I'm glad at least two people have got it working! Nice to know it's not too hard to set up I haven't experienced that problem myself yet. Hmm, I was wondering what would happen when it was stress tested. Perl $dir/rtorrent_fast_ $download $watch/$name Perl $dir/rtorrent_fast_ "$torrentpath" "$watch/$torrentname.$RANDOM.torrent"Ĭookie=`curl -vskm 1 -H "Content-Type: application/json" -X POST -d "" $scheme://$domain:$port/json # Remove torrent using $1 var passed from Execute. # If block ensures these lines don't run except via Execute plugin. # to rTorrent's watch directory, "watchr" for addition. # Every torrent, "f", will have fastresume data added and then moved If then tar -cf $HOME/deluge_state.$date.tar $files fi # Remember to chmod +x this script and the perl script! # # Please remember to have rTorrent fully setup and config'd! # # Please remember to create the watch folder for rTorrent! # # This script is designed to be used alongside the Execute plugin! # # Do not change this unless you have knowingly changed Deluge's # rm'ing it all? (Useful the first time for the mass-transfer but # Do you want to backup whatever's in Deluge's state directory before # Where do your torrents eventually download to? If they auto-move # Which folder are you keeping rtorrent_fast_ in? # Do you use http or https to access the WebUI (default http)? # The port you use to access the WebUI (default 8112) # Default is "deluge", but you should have changed it. In order to not have to start using two different web-interfaces, you could start using this UserScript to add torrents to Deluge (and hence rTorrent) with minimal effort (works on private trackers too) (use it with NinjaKit for Safari): torrent files every 24 hours: "crontab -e" and enter "0 0 * * * rm $HOME/path/to/rtorrent/watch_folder/*.torrent > /dev/null 2>&1" – unadvisable if you have schedule start_tied set.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |