Bug 853959 - Option -n (--no-tpm) missing in man page
Option -n (--no-tpm) missing in man page
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: man-pages-overrides (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Peter Schiffer
Petr Beňas
: ManPageChange, Patch
Depends On:
Blocks: 878458 886216
  Show dependency treegraph
Reported: 2012-09-03 08:23 EDT by Milan Broz
Modified: 2015-01-04 18:03 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: missing description of "--no-tpm" option in the rngd(8) manual page Consequence: incomplete documentation Fix: added missing description of "--no-tpm" option Result: complete documentation
Story Points: ---
Clone Of:
: 878458 (view as bug list)
Last Closed: 2013-02-21 05:54:27 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Proposed patch (874 bytes, patch)
2012-09-03 08:23 EDT, Milan Broz
no flags Details | Diff

  None (edit)
Description Milan Broz 2012-09-03 08:23:57 EDT
Created attachment 609366 [details]
Proposed patch

Description of problem:

While RHEL6 backports support for TPM RNG, the -n option is not mentioned in man page.

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

Patch with fix attached.
Comment 2 Jeff Garzik 2012-11-19 13:46:55 EST
ACK, yes, the patch is OK.  It is already upstream.
Comment 8 Petr Beňas 2012-12-13 09:59:18 EST
Reproduced in man-pages-overrides-6.4.0-1.el6.noarch and verified in man-pages-overrides-6.4.1-1.el6.noarch.
Comment 10 errata-xmlrpc 2013-02-21 05:54:27 EST
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.