Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 155348 - RHEL3-rg-bug-E: Wrong example for nfs client configuration (automount) in rh-docs
Summary: RHEL3-rg-bug-E: Wrong example for nfs client configuration (automount) in rh-...
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: rhel-rg
Version: 3.8
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Don Domingo
QA Contact: John Ha
Depends On:
TreeView+ depends on / blocked
Reported: 2005-04-19 13:19 UTC by Nicolas Scheibling
Modified: 2014-08-04 22:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-10-19 19:04:21 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Nicolas Scheibling 2005-04-19 13:19:34 UTC
Description of problem:
Example is wrong for nfs client configuration (automount) 

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

How reproducible:
Read the rg manual!

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Right Text (doc from rh 7.2)
look at the folowing line:
*  -fstype=nfs,soft,intr,rsize=8192,wsize=8192,nosuid

Wrong Text: (doc from rhel3)
*  -fstype=nfs,soft,intr,rsize=8192,wsize=8192,nosuid,tcp

Comment 2 Michael Hideo 2007-06-06 04:44:11 UTC
Adding 'cc for tracking

Comment 3 RHEL Product and Program Management 2007-10-19 19:04:21 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

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