Bug 55374 - Mount NFS server in kckstart post install
Summary: Mount NFS server in kckstart post install
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 7.2
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-10-30 16:13 UTC by Derrien
Modified: 2007-04-18 16:37 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-10-31 12:25:26 UTC
Embargoed:


Attachments (Terms of Use)

Description Derrien 2001-10-30 16:13:14 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; SunOS 5.7 sun4u)

Description of problem:
In post part of a kickstart install I mount a NFS directory to execute some
commands;
it works but it's quite long. On console 4 I got :

<5>portmap: server localhost not responding, timed out
<5>portmap: server localhost not responding, timed out
<4>lockd_up: makesock failed, error=-5
<5>portmap: server localhost not responding, timed out
<4>lock_down: no lockd running

What does that mean ?
Thanks.


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


How reproducible:
Always

Steps to Reproduce:
1.kickstart install
2.mount -t nfs xxx:/xxxx /xxx in post-install
3.
	

Additional info:

Comment 1 Michael Fulbright 2001-10-30 19:51:39 UTC
This should not be a problem if you are using the mount command in the anaconda
intall environment. If you are calling the mount command on the freshly
installed system, you need to pass a '-o nolock' on the mount command line.

Does that help?

Comment 2 Derrien 2001-10-31 12:25:21 UTC
'-o nolock' helps. Thanks.

Comment 3 Brent Fox 2001-10-31 13:35:58 UTC
Ok.  Thanks for your report.


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