Bug 1295737 - man page for hwclock doesn't include --compare option
Summary: man page for hwclock doesn't include --compare option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: util-linux-ng
Version: 6.7
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Karel Zak
QA Contact: Robin Hack
URL:
Whiteboard:
Depends On:
Blocks: 1270825
TreeView+ depends on / blocked
 
Reported: 2016-01-05 11:25 UTC by masanari iida
Modified: 2017-08-08 08:34 UTC (History)
3 users (show)

Fixed In Version: util-linux-ng-2.17.2-12.19.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-11 00:35:04 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0911 0 normal SHIPPED_LIVE util-linux-ng bug fix update 2016-05-10 22:52:01 UTC

Description masanari iida 2016-01-05 11:25:06 UTC 
Description of problem:
man page for hwclock doesn't include --compare option

Version-Release number of selected component (if applicable):
util-linux-ng-2.17.2-12.18.el6.x86_64


How reproducible:
Always

Steps to Reproduce:
1.  man hwclock 
2.
3.

Additional info:
Both Japanese man page as well as English man page for hwclock 
doesn't explain what is the "--compare" option.

From upstream

       -c, --compare
              Periodically compare the Hardware Clock to the System Time and
              output the difference every 10 seconds.  This will also print
              the frequency offset and tick.
Comment 5 errata-xmlrpc 2016-05-11 00:35:04 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.

https://rhn.redhat.com/errata/RHBA-2016-0911.html
Note You need to log in before you can comment on or make changes to this bug.