topic NFS question in Operating System - HP-UX

NFS question

Mihails Nikitins — Mon, 22 Nov 2004 06:03:01 GMT

Hi,

I'd like to have one NFS connection from my HP-UX host to a NFS serever without having plenty of running processes like biod.

I turned off NFS capabilities in /etc/rc.config.d/conf
NFS_CLIENT=0
NFS_SERVER=0

On the other hand I have a line like this in /etc/fstab
1.2.3.4:/share/something /mnt/somewhere nfs rw 0 0

The share can't be mounted automatically when the system boots up, however, I can mount NFS share by command 'mount -a'.
The only running NFS-like process is nfskd

Question. How to mount the share automatically when the system comes up without running plenty of daemons?

Thanks and points in advance for you comments about the problem and/or NFS architecture in HP-UX.

BR,
Mihails

Re: NFS question

G. Vrijhoeven — Mon, 22 Nov 2004 07:05:36 GMT

Hi Mihails,

I would turn on the NFSCLIENT in the /etc/rc.config.d/ and do a /sbin/init.d/nfs.client start. This also starts boid so performance will inprove.

HTH,

Gideon

Re: NFS question

Wim Rombauts — Mon, 22 Nov 2004 07:36:29 GMT

If you have only one single NFS-mounted filesystem that you don't use that much, you can lower parameter NUM_NFSIOD in /etc/rc.config.d/nfsconf to 2 or 3. That will create a limited number of biod processes.
You will have to enable NFS_CLIENT also.
This will allow the NFS-filesystem to be mounted at boot time with only a limited set of daemons.

Re: NFS question

Mihails Nikitins — Mon, 22 Nov 2004 07:46:21 GMT

Hmmmm-mmmm, on the other hand I can just add a mount command to rc.local script....

Re: NFS question

Ivajlo Yanakiev — Mon, 22 Nov 2004 08:00:25 GMT

If you use NFS from time to time you can make one simple shell file, which will start nfs client mount your remoute FS and after finish your work you can umount and stop nfs client.
If you want ot start it on boot place this script in /sbin/init.d/ and link it in proper run level.

Re: NFS question

Elmar P. Kolkman — Wed, 24 Nov 2004 01:15:18 GMT

Turning off the NFS_CLIENT in nfsconf will give problems when processes like to do things like file locks... We ran into this causing logins to hang seemingly forever (home dirs were NFS mounted, while the NFS_CLIENT parameter was zero). It's better to lower other parameters so the number of other processes is lowered. For instance, START_MOUNTD=0, AUTOMOUNT=0, AUTOFS=0 and everything even works with NFSIOD=0 (just no caching). That way at least the lockd is started, which proved quite essential in some simple cases...