Red Hat Bugzilla – Bug 514427
start (nfs-utils) services that will be on in the current runlevel
Last modified: 2010-10-19 04:57:06 EDT
Description of problem:
nfs mount(s) unavailable even after nfs-utils is installed
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.try to mount nfs filesystem
/usr/sbin/start-statd: line 8: /sbin/rpc.statd: Permission denied
/usr/sbin/start-statd: line 8: /sbin/rpc.statd: Success
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
Don't think, "reboot". That's like Microsoft.
Be proactive. Think, "I'll help the users not have to know or care about his".
(In reply to comment #0)
> Be proactive. Think, "I'll help the users not have to know or care about his".
s/about his/about this/
Though, maybe not, as "service nfs start" from a konsole brought the desktop to a (unusable) crawl at the starting "NFS daemon" point.
Problem there, however, is you've assumed I'm starting an NFS server. When you assume...
Bottom line, logically, is start nfslock. (and, for that matter, chkconfig everything else "off".)
what are the mode bits on '/sbin/rpc.statd'? (ala ls -l /sbin/rpc.statd)
Is SELinux enabled?
I wonder if https://bugzilla.redhat.com/show_bug.cgi?id=513481 is
the problem here as well...
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
In F13, installing nfs-utils and nfs-utils-lib fails to have service nfs "on" as reported by "chkconfig -- list". Workaround is to manually change the levels.
Edit comment 5. "NFS" service not required to act as client. Not sure what the earlier issues were; it took an install of nfs-utils and a reboot for it to work the first time. Afterwards, removing nfs-utils, rebooting, and re-installing let the client mount properly.
Tossup between possible operator error and nfs-utils installing something the first time that fixed the issue and then not removing it when the rpm was pulled.
Its unclear to me this is a problem... Its on purpose the NFS server
is not on (i.e. chkconfig on) by default.. So I'm going to close this
bz, please feel free to reopen it.
(In reply to comment #7)
> Its unclear to me this is a problem... Its on purpose the NFS server
> is not on (i.e. chkconfig on) by default.. So I'm going to close this
> bz, please feel free to reopen it.
For comment #6, it took a nfs-utils and reboot to get the machine to act as an NFS client. Would you agree that is a bug?