Bug 126934

Summary:	Example 9.7.1 isn't complete
Product:	Red Hat Enterprise Linux 3	Reporter:	Joshua Weage <weage98>
Component:	rhel-sag	Assignee:	Sandra Moore <smoore>
Status:	CLOSED NEXTRELEASE	QA Contact:	John Ha <jha>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0	CC:	adstrong, andriusb, katzj, steved
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-02-03 21:13:24 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:
Bug Depends On:
Bug Blocks:	123819

Description Joshua Weage 2004-06-29 13:21:23 UTC

Description of problem:

The example of using an NFS server during a kickstart installation is
not quite complete.  Mounting an NFS share without using the "-o
nolock" option causes severe performance problems during a kickstart
install.  I suggest adding "-o nolock" to the example in the manual -
and maybe mentioning that NFS file locking isn't supported while in
kickstart mode.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 4 Andrius Benokraitis 2005-02-03 21:13:24 UTC

Joshua,

After consulting with the Red Hat developer assigned to post-install
scripts, you are correct! The mount binary is changed to '-o nolock'
by default, but would need to be set for the custom post-install
section...

The fix will go live for our next release of Red Hat Enterprise Linux.

Thanks so much for filing a bug to make our products better! :-)

Please do not hesitate to contact me for any futher questions or
comments! :-)

Andrius.