On Sun, Dec 17, 2017 at 11:44 AM, Chris Murphy <lists(a)colorremedies.com> wrote:
On Sun, Dec 17, 2017 at 8:41 AM, Dr J Austin <ja(a)jaa.org.uk>
> I gave up using ldap/autofs some time ago and until the last
> the _netdev option in fstab (or something else maybe) has been working perfectly.
> 188.8.131.52:/home /home nfs4 defaults,_netdev 0 0
> 184.108.40.206:/global /global nfs4 defaults,_netdev 0 0
a. defaults + _netdev is confusing, it should be defaults by itself
Confusing, possibly. But correct, even though redundant. But I'd agree
that it should only be used if no other options are set.
b. instead of _netdev you probably want some combination of the
I always use that combination for /boot/efi, local data volumes in
/srv, and for network shares.
Also, fstab should include a valid hostname rather than IP, I think
it's trying to mount when the network interface alone is up but there
still are not other NFS dependent services including dhcp, so if you
include the name here, all of those thing will have to come up before
the connection is even attempted.
"noauto,x-systemd.automount" would work but is it what the OP wants?
He could've used autofs if he wanted an automount and didn't know
about systemd's integrated automount feature.
My understanding of NetworkManager-wait-online is to make sure that
network connections are disconnected before the network is taken down
on a reboot/shutdown. I don't know what its role is during startup.
There's a lot more here:
It's surprising that the Arch wiki doesn't mention startup.
In the same way that the wait-online unit ensures that the nfs shares
are unmounted before the network is taken down, it ensures that the
network is up before the nfs shares are mounted.