Skip to content
This repository has been archived by the owner on Feb 24, 2022. It is now read-only.

rtorrent process not gracefully terminated #58

Closed
deed02392 opened this issue Aug 19, 2017 · 2 comments
Closed

rtorrent process not gracefully terminated #58

deed02392 opened this issue Aug 19, 2017 · 2 comments

Comments

@deed02392
Copy link

When running docker stop on this container, the rtorrent lock file is not deleted.

The fact this lock file is left behind indicates rtorrent isn't gracefully shutting down. This can cause issues with state data in rtorrent.
@deed02392 deed02392 mentioned this issue Aug 20, 2017
Closed
@sparklyballs
Copy link
Contributor

non-issue arising from unsupported use of /config mounted on nfs shares

@deed02392
Copy link
Author

Wrong again @sparklyballs . I already tested this on a local fs mount for /config and rtorrent.lock is not removed. Otherwise I suspect you wouldn't have included the 'rm' command as part of the cont-init script in the first place.

@aptalca aptalca mentioned this issue Sep 16, 2017
Closed
@deed02392 deed02392 mentioned this issue Sep 15, 2018
Closed
@themightykitten themightykitten mentioned this issue Feb 4, 2019
Closed
@jorritsmit jorritsmit mentioned this issue May 6, 2020
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix rtorrent shut down linuxserver/docker-rutorrent
2 participants
@deed02392 @sparklyballs