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.
Bug 659720 - manpage not in sync with options logrotate actually recognizes
Summary: manpage not in sync with options logrotate actually recognizes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: logrotate
Version: 6.1
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Jan Kaluža
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On: 642936 644308
Blocks: MPO-6.3-REMOVE
TreeView+ depends on / blocked
 
Reported: 2010-12-03 15:02 UTC by Ivana Varekova
Modified: 2012-06-20 12:39 UTC (History)
7 users (show)

Fixed In Version: logrotate-3.7.8-15.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 644308
Environment:
Last Closed: 2012-06-20 12:39:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0786 0 normal SHIPPED_LIVE logrotate bug fix and enhancement update 2012-06-19 20:34:43 UTC

Description Ivana Varekova 2010-12-03 15:02:11 UTC
+++ This bug was initially created as a clone of Bug #644308 +++

+++ This bug was initially created as a clone of Bug #642936 +++

Version-Release number of selected component (if applicable):
logrotate-3.7.4-9.el5_5.1

Steps to Reproduce:
# ./compare-options.sh /usr/sbin/logrotate 
Program path:
	/usr/sbin/logrotate
Man pages found:
	/usr/share/man/man8/logrotate.8.gz
The binary analysis was NOT done
Doing man page vs. usage message comparison

The program reported 13 option(s)
The man page reported 12 option(s)
9 COMMON option(s):
	--force
	--mail
	--state
	--usage
	-d
	-f
	-m
	-s
	-v
4 option(s) reported by the program ONLY:
	--debug
	--help
	--verbose
	-?
3 option(s) reported by the man page ONLY:
	-HUP
	-dv
	-force

-HUP is false positive (it is used in text like an example of killall)
-dv is false positive (it is combination of -d and -v)

Actual results: 
no all parameters of program are in man page and 1 in man page is wrong (typo)

Expected results:
all parameters in program and man page are same

--- Additional comment from jkaluza on 2010-10-19 07:46:28 EDT ---

Created attachment 454331 [details]
proposed patch

This patch corrects the man page.

Comment 8 errata-xmlrpc 2012-06-20 12:39:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0786.html


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