After working around systemd's insistence on trying to mount network filing systems before the network is up, I thought I would add a comment (probably as "command explanations" in "optional" markup to the Client Configuration part of nfs-utils).
https://bugzilla.redhat.com/show_bug.cgi?id=1027114 summarises the problem. But what we actually have in the book is so different from what I'm passing as mount options that I wonder if it would be better to update it all ? The current book has two examples - /home mounted r/w and /usr mounted r/o. <server-name>:/home /home nfs rw,_netdev,rsize=8192,wsize=8192 0 0 <server-name>:/usr /usr nfs ro,_netdev,rsize=8192 0 0 My own mounts are all NFSv3 using tcp, and all specify hard, intr, tcp, vers=3 [ that latter has been required for quite some time, possibly to prevent mount trying to use NFSv4 code, but I no longer remember the details ]. My shares which are to be mounted automatically all have _netdev and now on systemd comment=systemd.automount as the last option. My shares which are not to be mounted automatically have noauto and some of them also have user. Note also that I nver specify rsize or wsize. So, there is a lot of possible variation here. But I guess somebody might still be using NFSv2, and perhaps someone in the community is using NFSv4. I know nothing about current options for either of those. Is it worth me putting some / any of this into the NFS Utilities page ? ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
