Custom Query (2449 matches)


Show under each result:

Results (127 - 129 of 2449)

Ticket Resolution Summary Owner Reporter
#2366 Duplicate Location of deluge pid file tuusjr

Currently, the deluge pid file is located under $XDG_CONFIG_DIR, which may force the user to manually delete the pid file on unclean exits, eg power failure. If the location of the pid file was to use the $XDG_RUNTIME_DIR specification, this situation would be remedied.

Exerpt of the standard according to

"The lifetime of the directory MUST be bound to the user being logged in. It MUST be created when the user first logs in and if the user fully logs out the directory MUST be removed. If the user logs in more than once he should get pointed to the same directory, and it is mandatory that the directory continues to exist from his first login to his last logout on the system, and not removed in between. Files in the directory MUST not survive reboot or a full logout/login cycle."

The specification ensures that a pid file will not survive on a reboot or login/logout cycle. Thus, using $XDG_RUNTIME_DIR remedies this situation.

#938 WontFix [NAT] Friendly peers permanent list andar

Our city net is under NAT (192.168.*.*). Traffic between peers in city are payable, but unpaid inside one house.

We ban all city IPs, but allow in-house IPs.

ISP use shaper therefore global net is slow. But we often download one torrent together (in parts by files). It will be helpfully if we can fill up permanent peer list with our in-house IPs. So we can download torrent faster.

#772 Invalid Deluge not running due the sha module is deprecated andar

Just updated to 1.1.1 and got this error:

$ deluge /usr/lib/python2.6/site-packages/deluge/ui/ DeprecationWarning?: the sha module is deprecated; use the hashlib module instead

from sha import sha


Note: See TracQuery for help on using queries.