#3044: Restarting deluged via systemd causes errornous torrents
----------------------+------------------------------------
Reporter: krichter | Owner:
Type: bug | Status: new
Priority: minor | Milestone: needs verified
Component: Unknown | Version: other (please specify)
Keywords: |
----------------------+------------------------------------
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
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/3044>
Deluge <http://deluge-torrent.org/>
Deluge Project
--
You received this message because you are subscribed to the Google Groups
"Deluge Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/deluge-dev.
For more options, visit https://groups.google.com/d/optout.
