Custom Query (2449 matches)

i have the impression, that the peers to whom deluge tries to connect are selected from the highest ip number down to the lower ones (starting above 220.x.x.x)
I don't know if this is correct, but this is not a good behaviour. random or sorted by ping-time would be much better, because here in europe always starting with peers in australia and the far east doesn't make much sense.

I'm downloading a torrent which contains several files. While the torrent still not fully downloaded (on compact allocation mode), the completed files are not visible on hard disk.

ways to reproduce the bug:

1. start downloading a torrent (a movie torrent will do - most movie torrents contain the main movie file and a much smaller sample file).
2. most chances are that the smaller file (the sample clip in our example) will be fully downloaded first.
3. after it does (while the torrent is still not fully downloaded) - go to your temporary downloads folder and see that the sample file is not there.
4. pause the torrent and check again - the file will suddenly appear.

this only happens with small (2-5mb) files.

I'm using the version on ubuntu gutsy repositories: 0.5.4.1

thanks :)

Situation: there were multiple files or multiple directories in a torrent, I choose not to download some of them before download begins. But deluge will still create the files (directories) that were choosen not to download. This was inconvenient when there was much file in a torrent and I only want to download very few of them.