Move Completed Moves Files That Should Not Be Moved
Posted: Sat Feb 21, 2009 9:04 pm
So I'm running 1.1.2 and I have my settings so that completed files are moved to the folder "Seeding". But I often want to move the files to another directory and keep seeding them. However, I run into the following problem:
I have about 40 files that I want to seed from their own folders, not the Seeding folder.
When I open Deluge (like after a system restart), it seems like there is some sort of race condition between starting to seed and moving files.
Out of the 40, a random number of them will magically have moved to the Seeding folder after they have begun seeding, as if I had just downloaded them.
I can move them back to the correct folder and Deluge behaves until a SYSTEM restart.
The only way these files can move is if Deluge is moving them, so there is clearly some kind of issue with the meaning of "completed," so I guess the files technically represent "completed" torrents. But to make it an effective feature, the move should only occur after a file transitions from a "downloading" to a "completed" or "seeding" state. Maybe when deluge starts all torrents are briefly in the "downloading" state? That would also be bad.
Anyway, I would much appreciate it if this feature is fixed. I'm sorry that I don't know enough about the mechanics of Deluge to give a more detailed description, like how it actually assigns torrent state and the flags which actually trigger a move.
Thanks.
~Sentinel
EDIT: So I noticed the problem only arises after a system restart, which is very very strange because from the user's perspective, the files are really moving, but maybe they're not actually moving? I'm running Ubuntu 8.10 (Intrepid). Could it be that there is something horribly wrong with file handling? Like the user interface not matching actual directory structure? I'm so confused.
I have about 40 files that I want to seed from their own folders, not the Seeding folder.
When I open Deluge (like after a system restart), it seems like there is some sort of race condition between starting to seed and moving files.
Out of the 40, a random number of them will magically have moved to the Seeding folder after they have begun seeding, as if I had just downloaded them.
I can move them back to the correct folder and Deluge behaves until a SYSTEM restart.
The only way these files can move is if Deluge is moving them, so there is clearly some kind of issue with the meaning of "completed," so I guess the files technically represent "completed" torrents. But to make it an effective feature, the move should only occur after a file transitions from a "downloading" to a "completed" or "seeding" state. Maybe when deluge starts all torrents are briefly in the "downloading" state? That would also be bad.
Anyway, I would much appreciate it if this feature is fixed. I'm sorry that I don't know enough about the mechanics of Deluge to give a more detailed description, like how it actually assigns torrent state and the flags which actually trigger a move.
Thanks.
~Sentinel
EDIT: So I noticed the problem only arises after a system restart, which is very very strange because from the user's perspective, the files are really moving, but maybe they're not actually moving? I'm running Ubuntu 8.10 (Intrepid). Could it be that there is something horribly wrong with file handling? Like the user interface not matching actual directory structure? I'm so confused.