It can replace vixie-cron easily and is actively developed by upstream, while vixie-cron looks to be stalled. Then, I think cronie should be the first option Thanks
+1 for this, simple tests discovers no problems with cronie. And i use it on regular basis for couple of monthes or so.
*** Bug 494182 has been marked as a duplicate of this bug. ***
Will commit it next week if nobody disagrees
Several people have noticed rather increased log spamming since cronie b y default (?) goes through pam, and therefore every 5-10 minutes spams auth.log. Other distributions had the same problem, but commonly found solutions from Ubuntu- and Fedora forums are all mostly wrong, misleading or don't apply. Instead of massively complicated & fragile post-log filtering it is IMHO better to prevent this in the first place (if cron is not authorized yiu have more severe problems anyway..), so I dug into PAM and fixed it thus: $cat /etc/pam.d/crond # # The PAM configuration file for the cron daemon # # auth include system-auth account required pam_access.so account include system-auth session required pam_loginuid.so session sufficient pam_succeed_if.so service in crond quiet use_uid ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ session include system-auth The marked line is new and silences PAM logging without completely disabling it. Maybe some one who really understands the PAM auth chain can improve on this before it becomes the default.
I haven't noticed that increase in logging, anyway, you should open a separate bug report against cronie
this was landed with virtual/cron-0-r1 so there's nothing left here if you have issues with cronie itself, please file a new bug
