#10203: systemd configuration for nfs-client (only) does not work properly
----------------------+------------------
Reporter: bdubbs@… | Owner:
Type: defect | Status: new
Priority: normal | Milestone: 8.2
Component: systemd | Version: SVN
Severity: normal | Resolution:
Keywords: |
----------------------+------------------
Comment (by bdubbs@…):
I ran into another problem at boot time. I did not have nfsd in the
kernel and was getting some warnings in the boot sequence. The book does
say to enable nfsd if you want the server, but if you only wast the
client, it is better to fix the nfs-client service to start rpc.statd.
This may not be necessary when we update to nfs-utils 2.3.1, In the NEWS
file:
- /sbin/{u,}mount.nfs{,4} are now installed so 'mount' will
use these to mount nfs filesystems instead of internal code.
- mount.nfs will check for 'statd' to be running when mounting
a filesystem which requires it. If it is not running it will
run "/usr/sbin/start-statd" to try to start it.
If statd is not running and cannot be started, mount.nfs will
refuse to mount the filesystem and will suggest the 'nolock'
option.
--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/10203#comment:1>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
