Custom Query (2447 matches)

Version is 0.5.9.3 I've accidentaly deleted my "auto download" folder and now deluge doesn't want to start

lafontaine@lafontaine-desktop:~$ deluge
no existing Deluge session
Starting new Deluge session...
deluge_core; using libtorrent 0.13.0.0. Compiled with NDEBUG.
Applying preferences
save uploaded memory
Pickling state...
Scanning plugin dir /usr/share/deluge/plugins
Initialising plugin TorrentNotification
Initialising plugin Search
Initialising plugin TorrentCreator
Initialising plugin NetworkGraph
Initialising plugin MoveTorrent
Initialising plugin EventLogging
Initialising plugin Scheduler
Initialising plugin TorrentPeers
Initialising plugin BlocklistImport
Initialising plugin DesiredRatio
Initialising plugin WebSeed
Initialising plugin TorrentFiles
Initialising plugin WebUi
Initialising plugin FlexRSS
Initialising plugin SpeedLimiter
Initialising plugin NetworkHealth
Applying preferences
Showing window
Traceback (most recent call last):
  File "/usr/bin/deluge", line 132, in <module>
    start_deluge()
  File "/usr/bin/deluge", line 116, in start_deluge
    interface.start(get_cmd_line_torrents())
  File "/var/lib/python-support/python2.5/deluge/interface.py", line 1034, in start
    self.update()
  File "/var/lib/python-support/python2.5/deluge/interface.py", line 1101, in update
    for filename in os.listdir(self.config.get("default_autoload_path")):
OSError: [Errno 2] Aucun fichier ou dossier de ce type: '<Here is my auto download folder>'

This is the issue explained here: ​http://forum.deluge-torrent.org/viewtopic.php?f=7&t=7055

Deluge is not completing the blocks during downloading any torrents, leading to much smaller file completion reports than overall completion, difficulty in seeding, and potential huge data loss on any recheck. (Which happened to me once)

Probably the same bug also means files marked "Highest" are not much faster to download than others, or at least take much longer than they did before.

Possibly this is a new/'improved' parts selecting algorithm?

(I have submitted this under "critical", as I believe it is a critical issue, however I am unfamiliar with this system, so please change it if you do not agree.)

Setting ToS can be extremely handy for routers supporting traffic shaping options etc, to allow qualifying all data as throughput for example. This becomes increasingly important as more bittorrent data is using random ports and encryption.

And it should be very easy to implement.

rtorrent (using the same library?) supports this for example: tos = default|lowdelay|throughput|reliability|mincost, tos = hex

Change the TOS of peer connections, by default set to throughput. If the option is set to default then the system default TOS is used. A hex value may be used for non-standard settings.