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#48236 - [atop] cron.d configuration invalid
Attached to Project:
Community Packages
Opened by ... (spider007) - Thursday, 18 February 2016, 11:54 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 10 March 2016, 18:20 GMT
Opened by ... (spider007) - Thursday, 18 February 2016, 11:54 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 10 March 2016, 18:20 GMT
|
DetailsDescription:
atop ships with a file in /etc/cron.d/atop; it contains: # daily restart of atop at midnight 0 0 * * * systemctl restart atop This is obviously incorrect; it should be: # daily restart of atop at midnight 0 0 * * * root systemctl restart atop |
This task depends upon
The timer question was brought up in another ticket.
Jobs in /etc/cron.d/
The jobs in cron.d and /etc/crontab are system jobs, which are used
usually for more than one user, thus, additionally the username is
needed. MAILTO on the first line is optional.