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#65529 - [atop] systemd accounting service not working.
Attached to Project:
Community Packages
Opened by bartus (bartus) - Monday, 17 February 2020, 13:11 GMT
Last edited by freswa (frederik) - Saturday, 29 February 2020, 15:29 GMT
Opened by bartus (bartus) - Monday, 17 February 2020, 13:11 GMT
Last edited by freswa (frederik) - Saturday, 29 February 2020, 15:29 GMT
|
DetailsCurrent localization of pid file is reported as incorrect by systemd.
` systemd[1]: /usr/lib/systemd/system/atopacct.service:10: PIDFile= references a path below legacy directory /var/run/, updating /var/run/atopacctd.pid → /run/atopacctd.pid; please update the unit file accordingly. ` This somehow is preventing atop from reporting exited processes. Changing PIDFile location fixes the issue `IDFile=/run/atopacctd.pid` |
This task depends upon
Closed by freswa (frederik)
Saturday, 29 February 2020, 15:29 GMT
Reason for closing: Not a bug
Additional comments about closing: Reporter: The problem is caused by something else than `PIDFile` location. After each reboot, I've to restart `atopacctd` in order for accounting to work.
Saturday, 29 February 2020, 15:29 GMT
Reason for closing: Not a bug
Additional comments about closing: Reporter: The problem is caused by something else than `PIDFile` location. After each reboot, I've to restart `atopacctd` in order for accounting to work.
Comment by Ike Devolder (BlackEagle) -
Thursday, 20 February 2020, 18:14 GMT
Sorry I cannot reproduce this issue, atopacctd seems to run just fine
Comment by bartus (bartus) -
Thursday, 20 February 2020, 23:25 GMT
Strange, as I'm having this issue on Arch but not on Manjaro system :/
Comment by Ike Devolder (BlackEagle) -
Saturday, 29 February 2020, 10:14 GMT
the /var/run symlink should be part of your system since its part of the filesystem package