Custom Query (2448 matches)

I'm managing deluged with the following systemd unit:

[Unit]
Description=Deluge Bittorrent daemon
Requires=network.target

[Service]
Type=simple
#forking
User=debian-deluged
Group=debian-deluged
LimitNOFILE=500000
ExecStart=/usr/bin/deluged --do-not-daemonize --config /var/lib/deluge/deluged/ --logfile /var/log/deluged/deluged.log

[Install]
WantedBy=multi-user.target

When I restart deluged with sudo systemctl stop deluged.service a random number of torrents is marked errornous and has to be force-rechecked.

#3028 is about corruption happening when the torrents are moved which is not the case in this issue - assuming that there's no move happening during restart.

experienced with 2.0.0.dev7019+fefe742+201705201502~ubuntu17.04.1 on Ubuntu 17.04

As of libtorrent 1.1.3, the boost=source, geoip=static, and encryption=openssl arguments for b2.exe aren't working. At ​http://libtorrent.org/building.html, geoip isn't listed as a build feature and the argument for setting openssl as the encryption method is "crypto", not "encryption."

It'd be great if ​http://dev.deluge-torrent.org/wiki/Building/libtorrent was updated to reflect these changes

The "name" option of a torrent is used for display purposes ​https://github.com/deluge-torrent/deluge/blob/develop/deluge/core/torrent.py#L128

In particular, it appears that several consecutive space (0x20) characters are coalesced into one. This can be easily verified by creating a torrent file for a file named

Untitled  .txt

(note the two spaces) and then looking at the entry in the torrent list in e.g. WebUI, which is

Untitled .txt

(one space).

The file written to disk, however, retains the original name with two spaces. This becomes a problem when using the Execute plugin, because it reads the display name ​https://github.com/deluge-torrent/deluge/blob/develop/deluge/plugins/Execute/deluge/plugins/execute/core.py#L98, which then has no relation to the actual filename, rendering it useless for all file operations.

I am not entirely sure where the coalescing happens, perhaps here ​https://github.com/deluge-torrent/deluge/blob/develop/deluge/core/torrentmanager.py#L331, neither am I sure about the best way to correct this. If the coalescing is intentional for display purposes, then the Execute plugin probably should not read the name option and instead read the name of the top-most file of a torrent.