Bug 115431 - typo in section 6.1.2 of "Red Hat Enterprise Linux 3: System Administration Guide"
Summary: typo in section 6.1.2 of "Red Hat Enterprise Linux 3: System Administration G...
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: rhel-sag   
(Show other bugs)
Version: 3.8
Hardware: All Linux
Target Milestone: ---
Assignee: Don Domingo
QA Contact: John Ha
Keywords: Documentation
Depends On:
TreeView+ depends on / blocked
Reported: 2004-02-12 13:44 UTC by James Laska
Modified: 2014-08-04 22:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 19:30:06 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

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

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

Comment 2 RHEL Product and 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:
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.