Red Hat Bugzilla – Bug 1025883
cronie-anacron enabled by default on server installations.
Last modified: 2014-03-20 11:00:06 EDT
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C; .NET4.0E; Tablet PC 2.0; InfoPath.3; MS-RTC EA 2; MS-RTC LM 8)
Bug causes unexpected behavior of cron and cron-like functions that anacron enables for server environments.
Servers in this era are expected to be up 24/7 rather than on an ad-hoc basis, and as such the inclusion of cronie-anacron causes some bizarre behavior that is totally unexpected in a server environment.
Steps to Reproduce:
1. Install server (any type) without customization.
2. cronie-anacron (used for non-server type systems) enabled by default.
cronie-anacron (which messes with expected traditional cron operation) is installed, which can cause issues with cron / startup entries being executed in an unexpected fashion.
On a server type installation, it is expected that it will be operational on a 24/7 basis.
Anacron is a tool used for desktops when the system may not be up on a 24/7 basis so that
The cronie-noanacron option should be the default for any server installation.
Servers are 24/7 devices, and the server install tree should not include anacron enabled by default.
The default action for any server setup should be to install cronie-noanacron for traditional cron behavior.
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
This behaviour change already happened five minor releases of RHEL back and change it now to something else would only make more broken servers.
I'm sorry for inconvenience, but the cronie upstream (mostly me) prefers cronie-anacron support.