Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#36535 - [darkstat] service fails to start after unclean shutdown
Attached to Project:
Community Packages
Opened by ajs124 (andy123) - Wednesday, 14 August 2013, 23:45 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 15 August 2013, 12:09 GMT
Opened by ajs124 (andy123) - Wednesday, 14 August 2013, 23:45 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 15 August 2013, 12:09 GMT
|
DetailsIf the system isn't shut down cleanly (power outage, kernel panic, …) darkstat doesn't start on the next boot.
Reproduce: Kill a machine with darkstat running and enabled (maybe a vm), boot it up again and observe that darkstat isn't running. Cause: My guess is that, since the PIDFile is on nonvolatile storage /var/darkstat/darkstat.pid instead of a tmpfs (/run) systemd gets confused. Fix: Add a /run/darkstat directory via tmpfiles and place the pidfile there. |
This task depends upon