Bug 659720 - manpage not in sync with options logrotate actually recognizes
Summary: manpage not in sync with options logrotate actually recognizes
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: logrotate
Version: 6.1
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Jan Kaluža
QA Contact: qe-baseos-daemons
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
Last Closed: 2012-06-20 12:39:59 UTC
Target Upstream Version:

Attachments (Terms of Use)

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):

Steps to Reproduce:
# ./compare-options.sh /usr/sbin/logrotate 
Program path:
Man pages found:
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):
4 option(s) reported by the program ONLY:
3 option(s) reported by the man page ONLY:

-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@redhat.com 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.


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