trickykid, i think you're right.
here's what I've learned since i posted
# service nfslock status
rpc.statd is stopped
#chkconfig --list nfslock
nfslock 0:off 1:off 2:off 3:on 4:on 5:on 6:off
# chkconfig --list portmap
portmap 0:off 1:off 2:off 3:on 4:on 5:on 6:off
# service portmap status
portmap (pid 702) is running..
# service nfslock start
<no message returned>
# service nfslock status
rpc.statd is stopped
# /sbin/rpc.statd
<no message returned>
# service nfslock status
rpc.statd is stopped
So its not running in the first place most likely
The nfslock service will run at runlevel 3, 4 and 5, so the service (which run rpc.lockd and rpc.statd) will run, but for some reason, it doesn't. Its not due to the portmapper, though, 'cause its running. I guess just because I don't use it.
|