Hide Forgot
Description of Problem: Now that the portmap service is on by default (due to the addition of sgi_fam), rpc.statd is on again by default (the nfslock service ships chkconfig-ed on, even though nfs ships chkconfig-ed off). In 7.1, while we ship 'chkconfig nfslock on', since portmap is off the nfslocking services are off. rpc.statd has been a source of remote-user security vulnerabilities in the past, and probably should not be turned on if it is not in use. We should set 'chkconfig nfslock off' by default unless there's an overriding reason not to do so.
Let the master to NOTABUG it :) /me washes hands
There are reasons for needing rpc.statd to run at boot. If you do a manual "service nfs on" for any reason, then crash while holding NFS locks, you'll end up never releasing that lock on the server, ever, unless you run rpc.statd on the subsequent reboot. It's rpc.statd which informs the server that the client reboot has happened and that lock cleanup must occur.