Opened 14 years ago
Closed 14 years ago
#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 (2)
comment:1 by , 14 years ago
| Component: | other → core |
|---|---|
| Priority: | minor → trivial |
| Status: | new → pending |
| Summary: | An option to choose torrent job state to be set after re-hashing is completed → Choose torrent state to be set after re-hashing is completed |
| Version: | 1.2.2 |
comment:2 by , 14 years ago
| Status: | pending → closed |
|---|
This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.
Note:
See TracTickets
for help on using tickets.
You can have a torrent paused and force recheck and it will not download. Could you clarify if this is what you mean?