Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to find out some details regarding cron and /etc/cron.d/ on a RedHat system. Ironically, my answer is viewable within the vixie-cron-*.src.rpm for this package, but the the man pages for cron don't match the text which is provided by the vixie-cron RPM.

If I search my MANPATH for the keyword cron, it shows me some results like vixie-cron (rpm). What does this (rpm) tag mean, why are these manpages not installed on the system and can I view those manpages?

$ man -k cron
/etc/anacrontab [anacrontab] (5)  - configuration file for anacron
anacron              (8)  - runs commands periodically
anacron             (rpm) - A cron-like program that can run jobs lost during downtime.
cron                 (8)  - daemon to execute scheduled commands (ISC Cron V4.1)
crontab              (1)  - maintain crontab files for individual users (ISC Cron V4.1)
crontab              (1p)  - schedule periodic background work
crontab              (5)  - tables for driving cron (ISC Cron V4.1)
crontabs            (rpm) - Root crontab files used to schedule the execution of programs.
vixie-cron          (rpm) - The Vixie cron daemon for executing specified programs at set times.

Note that there is no page for vixie-cron, and the vixie-cron package doesn't actually provide any manpages named vixie-cron

$ man vixie-cron
No manual entry for vixie-cron
$ rpm -q --whatprovides /usr/bin/crontab
$ rpm -q --list vixie-cron
share|improve this question
up vote 2 down vote accepted

The command man -k queries against a pre-compiled database and not the manual pages themselves.

I suspect that entries may have been made in the database (see man mandb for details) for pages that don't actually exist. I am not familiar enough with the RPM mechanisms to know how this could have happened.

In a similar vein, there is considerable flexibility in what section a given manual page may claim to live. For example, on my system man Carp claims to be in section "3perl" where the underlying file is stored in .../man3/Carp.3perl.gz. The commands

man Carp
man -s 3 Carp
man -s 3perl Carp

all yield the same page while man -s 3junk Carp complains that there is no such entry.

You might find mlocate (a.k.a. locate) to be useful for hunting files by name. I presume it is available for RedHat since redacted@redhat.com is credited as the author.

share|improve this answer
Regarding the statement "I suspect that entries may have been made in the database for pages that don't actually exist." -- These (rpm) entries show up on nearly most RHEL/CentOS system that I have access to, at different companies with different environments and procedures. This means that these rogue pages weren't added to the database by accident, and these entries exist due to a default option in the CentOS/RHEL operating system. – Stefan Lasiewski Dec 15 '10 at 23:00

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.