Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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)
Build Identifier:
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.
Reproducible: Always
Steps to Reproduce:
1. Install server (any type) without customization.
2. cronie-anacron (used for non-server type systems) enabled by default.
Actual Results:
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.
Expected Results:
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.
Comment 2RHEL Program Management
2013-11-04 20:25:35 UTC
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.
Comment 3Marcela Mašláňová
2014-03-20 15:00:06 UTC
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.