This looks like the standard well-know RH5.1 portmapper braindamage, that
if it's from the booting sequence (directly after Mounting remote
filesystems), except that if IT is that behavior it isn't exactly new
in 2.1.124, it's been there for ages (much longer than I have used 2.1,
which is quite a few versions)
The problem is that by default RH5.x (and probably older RH's too) start
up the portmapper AFTER it tries to mount NFS filesystems. This is of
course not a good idea (well, obvious NOW at least, it was probably best
described as dubious before), but it happened to work with Linux 2.0...
If you want to correct this one way to do it using RH's tools is:
# chkconfig --del portmap
Edit /etc/rc.d/init.d/portmap so that the chkconfig: line has sane
numbers (I used "345 13 96")
# chkconfig --add portmap
If you don't care about RH's toolset, it just as easy to just renumber the
links...
> nfsd_init: initialized fhcache, entries=256
> lockd_up: no pid, 3 users??
No idea about these, I haven't used knfsd yet, just the NFS client. It
could be follow-on problems from the late start of portmapper, so check
that first.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/