Portmap vs. nfs lockd
Charles G Waldman (firstname.lastname@example.org)
Fri, 21 May 1999 12:37:09 -0500 (CDT)
There seems to be an error in the startup sequence of RedHat 5.x (and
the Fermi Linux distributions derived from it). The startup file
/etc/rc3.d/S15nfsfs which mounts remote filesystems runs before the
file S40portmap which starts the portmapper. If the NFS mounts are
not specified with the "nolock" option, the NFS mount tries to contact
the lock daemon, which produces warning messages because the
portmapper hasn't been started yet. Some newsgroup postings suggest
mounting NFS filesystems with the "nolock" option, but of course this
disables file-locking. It seems to me that a better fix would be to
start the portmapper before doing NFS mounts. On my system, I've
renamed S40portmap to S14portmap so that it runs before S15nfsfs.
Also I've renamed K65portmap to K96portmap to prevent a similar
problem on shutdown - NFS mounts should be dismounted *before* turning
off the portmapper.
This setup change fixes the problem for me; can anyone see any
potential problem with doing this?