Community Packages

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!
Tasklist

FS#50699 - [atop] /etc/cron.d/atop always restarts atop, even if it wasn't enabled

Attached to Project: Community Packages
Opened by Chris Down (cdown) - Wednesday, 07 September 2016, 23:11 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 17 November 2016, 14:44 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

/etc/cron.d/atop always restarts atop, even if it wasn't enabled. It should check whether it was enabled, first, so as not to start it when it is disabled.

% cat /etc/cron.d/atop
# daily restart of atop at midnight
0 0 * * * root systemctl restart atop

% pacman -Q atop
atop 2.2_3-3
This task depends upon

Closed by  Sergej Pupykin (sergej)
Thursday, 17 November 2016, 14:44 GMT
Reason for closing:  Upstream
Comment by Doug Newgard (Scimmia) - Thursday, 08 September 2016, 14:20 GMT
The file in question comes from upstream, not from Arch. You'll likely want to talk to them.
Comment by Sergej Pupykin (sergej) - Thursday, 17 November 2016, 14:44 GMT
Please report upstream, probably they need to use "systemctl is-enabled atop && systemctl restart atop" in crontab for systemd. Or even better "systemctl try-restart atop".

Loading...