[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: running *only* NFSv4 on f12 produces rpc.mountd error

"Robert P. J. Day" <rpjday crashcourse ca> writes:
> #MOUNTD_NFS_V1="no"
> #MOUNTD_NFS_V2="no"
> #MOUNTD_NFS_V3="no"
>   so i uncomment all those lines to (allegedly) disable all earlier
> version support and:
> 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]

I put a bugzilla in on this back in the FC4 or 5 days.  The
MOUNTD_NFS_V1="no" is the error.  The current rpc.mound doesn't have any
"--no-nfs-version 1" flag and is complaining about that. (This v1 flag
stuff should really be taken out of /etc/sysconfig/nfs as well as
/etc/init.d/nfs .

To be nfsv4-only you will also want to add these other things to the
conf file.

# As a test, don't allow any nfs v1,v2,v3 service.  Only allow v4

# this causes errors.  /etc/inint.d/nfs Script mainanance issue.

# don't allow rpc.nfsd to process v2 or v3 requests either.
# we'd like to say 0, but that means kill the daemons including the nfs4 one.

# end

Wolfgang S. Rupprecht
If the airwaves belong to the public why does the public only get 3
non-overlapping WIFI channels?

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]