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

Re: Also having NFSv4 problems

>> >> http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Deployment_Guide/ch-nfs.html

>> >> |rpc.mountd| — This process receives mount requests from NFS
>> >> clients and verifies the requested file system is currently
>> >> exported. This process is started automatically by the |nfs|
>> >> service and does not require user configuration. This is not used
>> >> with NFSv4.

>> >   and if that's truly the case, then the NFS start script
>> > /etc/init.d/nfs should not try to invoke rpc.mountd (or rpc.statd
>> > for that matter) when it's obvious that you're trying to run
>> > exclusively with NFSv4, no?  if that's the case, i can bugzilla
>> > that as well but i want to make sure that it's really an error
>> > first.

>> I suppose a case could be made for that either way.  Seems rather
>> minor to me.

>> I've not yet had time to look a this stuff.  However, is there any
>> downside from starting rpc.mountd even if it isn't going to be used?

>  i don't know.  and it's not only rpc.mountd.  as i read it,
> rpc.statd *also* becomes superfluous.  and if there's no reason to run
> a daemon, i see no point in running it.  why waste the cycles?

rpc.mountd is failing to launch so it is not wasting cycles.

rpc.statd on the other hand is launching and
does say that it is not needed.

If you comment out the rpc.mountd and rpc.statd sections of
/etc/init.d/nfs (or back up /etc/init.d/nfs and delete them), can you
still mount your shares?

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