On Jun 22, 2024, at 10:34, Patrick Dupre via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > ls -la /etc/cron.weekly/ > > drwxr-xr-x. 2 root root 4096 Jun 22 16:14 . > drwxr-xr-x. 248 root root 20480 Jun 22 16:04 .. > -rwxr-xr-x. 1 root root 1685 Jun 8 16:17 backup3 > -rwxr-xr-x. 1 root root 3563 Jun 8 16:36 backup.cron > -rwxr-xr-x. 1 root root 3561 Jun 6 22:55 backup.cron.saved > > > Good, it seems that (during the update?), a backup.cron.saved has been created. > I guess that I can just moved to backup.cron_saved The Cron daemon will not modify those files, and that’s not the naming suffix that RPM updates will create, which would only happen if the file was a package anyway. You had to have created that file. Perhaps you forgot? Also, renaming it to yet another suffix will not stop it from running along side the backup.cron. You need to remove it from the directory to get it to stop executing a second cron job. -- Jonathan Billings -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
