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.
DescriptionJapheth Cleaver
2019-04-10 19:30:04 UTC
+++ This bug was initially created as a clone of Bug #1027240 +++
Below was never applied to EL7
============================
$ man run-parts
man: can't open /usr/share/man/man/man4/crontabs.4: No such file or directory
No manual entry for run-parts
$ zcat /usr/share/man/man4/run-parts.4.gz
.so man/man4/crontabs.4
Seems to be one "man" too much.
--- Additional comment from Fedora Update System on 2013-12-20 12:17:51 UTC ---
crontabs-1.11-7.20130830git.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/crontabs-1.11-7.20130830git.fc19
--- Additional comment from Fedora Update System on 2013-12-20 12:18:42 UTC ---
crontabs-1.11-7.20130830git.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/crontabs-1.11-7.20130830git.fc20
--- Additional comment from Fedora Update System on 2013-12-21 02:12:29 UTC ---
Package crontabs-1.11-7.20130830git.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing crontabs-1.11-7.20130830git.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-23706/crontabs-1.11-7.20130830git.fc19
then log in and leave karma (feedback).
--- Additional comment from Fedora Update System on 2013-12-24 03:41:28 UTC ---
crontabs-1.11-7.20130830git.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
--- Additional comment from Fedora Update System on 2014-01-29 03:15:19 UTC ---
crontabs-1.11-7.20130830git.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
================================
See also BZ#1054525. Manually changing the file contents to ".so man4/crontabs.4" and re-compressing fixes the issue.
Still present in RHEL 7.7
[root@rhel7-x86-64 ~]# rpm -q redhat-release-server crontabs
redhat-release-server-7.7-10.el7.x86_64
crontabs-1.11-6.20121102git.el7.noarch
[root@rhel7-x86-64 ~]# rpm -qV crontabs
[root@rhel7-x86-64 ~]# ll /usr/share/man/man4/run-parts.4.gz
-rw-r--r--. 1 root root 42 Dec 27 2013 /usr/share/man/man4/run-parts.4.gz
[root@rhel7-x86-64 ~]# man run-parts
man: can't open /usr/share/man/man/man4/crontabs.4: No such file or directory
No manual entry for run-parts
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 7 and therefore will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.