On Sun, Dec 17, 2017 at 8:41 AM, Dr J Austin <ja(a)jaa.org.uk> wrote:
On Sun, 2017-12-17 at 08:20 -0500, Tom Horsley wrote:
> On Sun, 17 Dec 2017 11:07:52 +0000
> Dr J Austin wrote:
> > Anyone else with the same problem/
> I gave up on getting NFS mounts to work a long time ago.
> I have a job I start with "at now" in rc.local that
> delays for a few seconds then does all the NFS mounts.
> I have other commands in there as well to delay the
> start of other services that need the network and
> often don't come up correctly in a normal boot.
> P.S. The use of "at now" is required by yet more
> stupidity introduced by systemd which seems to believe
> it desperately needs to keep track of everything
> started by rc.local despite the fact that rc.local
> has always been a place to put ad-hoc random junk.
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
I gave up using ldap/autofs some time ago and until the last update
the _netdev option in fstab (or something else maybe) has been working perfectly.
184.108.40.206:/home /home nfs4 defaults,_netdev 0 0
220.127.116.11:/global /global nfs4 defaults,_netdev 0 0
a. defaults + _netdev is confusing, it should be defaults by itself OR options
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.
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: