NLS Posted January 27, 2016 Report Share Posted January 27, 2016 Sometimes (esp. after big disk moves etc.) you need to start utorrent to edit torrent details but you don't want them started even if they were started (seeding or downloading) when client was closed.This would prevent unnecessary checks. Best implementation would be to have two parameters.\allstop - all torrents stopped (seeding/downloading/checking) when client starts\stop <torrentname> - to stop .torrent with that name (before extension), when client starts Would also be nice to run those parameters even with client running to actively stop from a script - but that would be a bonus. Link to comment Share on other sites More sharing options...
schnurlos Posted January 27, 2016 Report Share Posted January 27, 2016 I don't know if that helps or even if that works (not tested!), but google brought me that:https://code.google.com/archive/p/cutorrent/http://blog.utorrent.com/2013/01/24/introducing-btc-a-torrenting-shortcut/ Link to comment Share on other sites More sharing options...
NLS Posted January 27, 2016 Author Report Share Posted January 27, 2016 Interesting finds. This will satisfy the "would be nice" I talk about above but most probably NOT my main issue:To START a (non-running) uTorrent client with torrents that were left running (downloading/seeding or checking) as stopped.I want to prevent uTorrent accessing a torrent that I (say, mistakenly) left running before exiting the client.Why? Because if it moved while torrent was not running, it would trigger a fresh hash check and if the torrent is let say 1.3TB (yes I have such a torrent) it is more than painful. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.