[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 29/12/17 16:18, Julian Hall wrote: > On 29/12/17 14:37, Peter Walker wrote: >> >> On 29/12/17 13:36, Julian Hall wrote: >> >>> Yes it is, but you'll be pleased to know that since the last outing with the NFS >>> shares I have pared down the options so now all I have in the fstab is: >>> >>> # automount CASSIOPEIA on NAS >>> 192.168.1.3:/volume1/CASSIOPEIA /media/julian/CASSIOPEIA nfs >>> # automount DIANA on NAS >>> 192.168.1.3:/volume1/DIANA /media/julian/DIANA nfs >>> # automount PERSEPHONE on NAS >>> 192.168.1.3:/volume1/PERSEPHONE /media/julian/PERSEPHONE nfs >>> >>> Very little option for any screwups, I would hope. >> I'm jumping into this halfway through but won't having this in the fstab cause >> the NAS to be mounted at boot rather than automounted on demand? >> I have seen lots of race conditions on NFS and the network in various Linuxes of >> the past few years. Has needed lots of tweaks to systemd startup to make sure the >> network was there before the FS tried to mount. >> Proper automount should be far more resilient. >> >> Cheers, >> >> Pete >> >> > Mount at boot was the behaviour prior to kernel 4.13 and /is/ the desired > behaviour. No worries. I was just confused by the automount terminology and thought you were aiming at something like this https://wiki.archlinux.org/index.php/NFS#Mount_using_.2Fetc.2Ffstab_with_systemd Pete -- The Mailing List for the Devon & Cornwall LUG https://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq