Bug 115431

Summary:	typo in section 6.1.2 of "Red Hat Enterprise Linux 3: System Administration Guide"
Product:	Red Hat Enterprise Linux 3	Reporter:	James Laska <jlaska>
Component:	rhel-sag	Assignee:	Don Domingo <ddomingo>
Status:	CLOSED WONTFIX	QA Contact:	John Ha <jha>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.8	CC:	adstrong, ecs-dev-list, jturner
Target Milestone:	---	Keywords:	Documentation
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-10-19 19:30:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description James Laska 2004-02-12 13:44:19 UTC

URL:
https://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/sysadmin-guide/ch-disk-quotas.html#S1-DISK-QUOTAS-CONFIGURING

6.1.2. Remounting the File Systems

After adding the userquota and grpquota options, remount each file
system whose fstab entry has been modified. If the file system is not
in use by any process, use the umount command followed by the mount to
remount the file system. If the file system is currently in use, the
easiest method for remounting the file system is to reboot the system. 

The above paragraph refers to adding the *userquota* option to
/etc/fstab...this should read *usrquota*

Comment 1 Michael Hideo 2007-06-06 04:42:45 UTC

Adding 'cc ecs-dev-list for tracking

Comment 2 RHEL Program Management 2007-10-19 19:30:06 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:
http://www.redhat.com/security/updates/errata/
 
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.