Ticket #1357 (closed feature-request)
Choose torrent state to be set after re-hashing is completed
| Reported by: | Koroboru | Owned by: | |
|---|---|---|---|
| Priority: | trivial | Milestone: | Future |
| Component: | core | Version: | |
| Keywords: | option, state, re-hashing | Cc: |
Description
Currently after I rehash some torrent, Deluge begins to seed it if it's complete. It is fine. But if the torrent is incomplete, Deluge immediately starts to download it. This can make some problems in situation, for example, if I set the torrent data location to another file with same name. In this way, the existing file will be spoiled, because it fails hash-check and is immediately overwritten...
So I ask for an option which allow to choose not to start torrent job after re-hashing data.
Change History
Note: See
TracTickets for help on using
tickets.
