jkaberg
commented
11 years ago We could check for releases "to delete" with the criterias you mention when the script is run, but that could be unreliable if no torrents are downloaded in a long perioid of time. Perhaps a hybrid doing both these would perhaps be the best solution?
I just think we should bring this up-to-par with Deluge atleast aswell (I doubt I can get Transmission to work with this)
If this is what we will do, perhaps move the cronjob code to seperate file which can be called individually (which would have the sole purpose of checking and deleteing old torrents?)
Suggested criterias: minimum seed time, minimum ratio (more?)
berkona
clinton-hall
schumi2004
I'm not sure exactly what api options are available for utorrent... But we could call a number of api calls... If utorrent had a seed for x hours then delete... We could call it... http://www.utorrent.com/community/developers/webapi
They do have a http://[IP]:[PORT]/gui/?action=removedata&hash=[TORRENT HASH] This action removes the specified torrent job(s) from the torrent jobs list and removes the corresponding torrent contents (data) from disk. Multiple hashes may be specified to act on multiple torrent jobs. This action respects the option "Move to trash if possible".
So.. I wouldn't want the script looping for 24 hours... But what we could do is schedule a cron job to run in 24 hours time... But not sure if we can easily define the hash within the cron job...
Otherwise we could schedule a cron job to do regular checks (at defined intervals) to get the time since finish etc... Since utorrent does support a seed ratio and it appears from the link above that you can set a default seed time, perhaps these could be set there, and then a regular cron job could just remove torrents after x hours/days etc...
Otherwise we could write the torrent hash and end time into a file and have a regular cron job that would parse this file and when the times are met, call utorrent api to remove that torrent... And then remove the entry from that file...
The message below is from Rizo. This confirms that everything is currently working correctly (CPS and SB). Rizo is the originator of this potential enhancement.
................... [quote='Rizo'] Confirmed, all works well.
You got it, I'll have to make a github account and start updating parts I'm more comfortable with explaining. I'll try and start over the weekend when I'm done with my lab work.
On a side note, is there a list of parameters you can link me to so I define my own end command when renamer has run? After skimming the code, I tried editing the last bit:
[code]
Hardlink solution with uTorrent
if inputHash and useLink: Logger.debug("MAIN: Starting torrent %s in uTorrent", inputName) utorrentClass.start(inputHash)
[/code]
I see in client.py you've defined start, stop, pause, forcestart, etc. Say I wanted to stop and delete the torrent after 24 hrs of seeding (per BTN tracker rules), how would I go about that? I realize the script would be running continually, but that's fine.
Also this is a big one, but do you think it would be possible to vary the end command depending on what tracker the file is associated with? That would bring the script to god tier complete automation. :cool:
Like I said, legendary work man. Really nice script, thanks again.