On Sun, 3 Jan 2010, Robert G. (Doc) Savage wrote:
... snip ...
> The problem appears to be on the F12 client side:
>
> # service nfs restart
> Shutting down NFS mountd: [FAILED]
> Shutting down NFS daemon: [ OK ]
> Shutting down NFS quotas: [ OK ]
> Shutting down NFS services: [FAILED]
> Starting NFS services: [ OK ]
> Starting NFS quotas: [ OK ]
> Starting NFS daemon: [ OK ]
> Starting NFS mountd: Usage: rpc.mountd [-F|--foreground] [-h|--help] [-v|--version] [
> -d kind|--debug kind]
> [-o num|--descriptors num] [-f exports-file|--exports-file=file]
> [-p|--port port] [-V version|--nfs-version version]
> [-N version|--no-nfs-version version] [-n|--no-tcp]
> [-H ha-callout-prog] [-s|--state-directory-path path]
> [-g|--manage-gids] [-t num|--num-threads=num]
> [FAILED]
>
>
> About four years ago I was able to set up a similar arrangement
> using nfs3 on RHEL4 and F6, but this is my first attempt with nfs4.
> I seem to be having the same problem Robert P.J. Day is having with
> rpc.mountd.
a private emailer tells me that what's causing the problem above is
deselecting the NFSv1 line from /etc/sysconfig/nfs. apparently, that
causes the problem so you should try this:
#MOUNTD_NFS_V1="no"
MOUNTD_NFS_V2="no"
MOUNTD_NFS_V3="no"
weirdly, that fixes that last problem. why should that be?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines