Bug 223532 - [LSPP] crontab manpages reference older environment variable
[LSPP] crontab manpages reference older environment variable
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: vixie-cron (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Marcela Mašláňová
Brock Organ
Depends On:
Blocks: RHEL5LSPPCertTracker
  Show dependency treegraph
Reported: 2007-01-19 16:16 EST by Matt Anderson
Modified: 2007-11-30 17:07 EST (History)
4 users (show)

See Also:
Fixed In Version: RHBA-2007-0564
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-07 13:33:38 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Matt Anderson 2007-01-19 16:16:23 EST
Description of problem:
The crontab (5 & 8) man pages both reference an environment variable
SELINUX_ROLE_TYPE, this has been changed to MLS_LEVEL please update the docs

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. man crontab
2. man 5 crontab
Comment 1 Marcela Mašláňová 2007-01-22 04:13:55 EST
Patch for manual is available in devel. Should be in RHEL-5.
Comment 2 Irina Boverman 2007-02-14 15:36:15 EST
per 2/12 discussion, this should be changed to MODIFIED.
Comment 4 Matt Anderson 2007-03-13 15:45:42 EDT
There is a typo above, it should be the crontab man page for sections 1 and 5.

I just installed vixie-cron-4.1-66.2.el5.x86_64.rpm from sgrubb's LSPP repo and
both man pages still reference SELINUX_ROLE_TYPE.
Comment 5 Jay Turner 2007-03-20 08:42:44 EDT
QE ack for RHEL 5.1.
Comment 6 Matt Anderson 2007-03-20 11:06:00 EDT
The LSPP repo now contains vixie-cron-4.1.67.el5 which has the updated man pages
for both crontab(1) and crontab(5)
Comment 10 errata-xmlrpc 2007-11-07 13:33:38 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.