On 07/31/18 00:35, Bob Goodwin wrote:
On 07/30/18 12:01, Bob Goodwin wrote:
> On 07/30/18 10:57, Ed Greshko wrote:
>> In your fstab you can try changing it to something like....
>>
>> 192.168.1.86:/home/exports /mnt/testb nfs4
>> rw,soft,intr,fg,comment=systemd.automount 0 0
>>
>> You may not see it mounted at boot time but as soon as you access the directory
it
>> will become mounted.
>>
>> At least that is the way I fixed a problem with NFS mounts of a NAS.
>>
>> --
> +
> No that did not work either, I copied/pasted and replaced the existing line.
> However it still boots from a terminal after the client is up.
>
> The server is always running, I shut the clients down at night, whatever.
>
> Maybe it is "NetworkManager-wait-online.service"related then? Although it
used to
> always just work. Perhaps a recent update coincident with my other system changes
> is responsible, but Ed apparently doesn't see the problem there?
>
+
I had the same result on the Fedora 28 computer, had to mount it manually ...
If you do
journalctl -b 0 | grep mount
on the client, what does it show?
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.