@Aki This gives back systemd "/sbin/init -> /lib/systemd/systemd"
I still haven't got it to work. What's even more annoying now though, after turning off one of my NFS servers, I cannot mount that directory anymore. When I try to mount, umount etc. I always get "mount.nfs: Stale file handle". I realize this is expected behaviour, when connection is lost without unmounting - however it's irritating that this is the default (especially as, unlike for seemingly everyone else, I've got no way to ever mount the directory again because of that error, which survives restarting init.d/nfs AND rebooting the server?)
On a reddit thread on the topic, I've stumbled upon the recommendation to use systemd automount instead of autofs. I might give this a try if I can't get this to work any other way.
A hunch I've got just now - is it possible that fstab does not work because the mounted directory is not in /mnt/ but in my home directory instead?
I still haven't got it to work. What's even more annoying now though, after turning off one of my NFS servers, I cannot mount that directory anymore. When I try to mount, umount etc. I always get "mount.nfs: Stale file handle". I realize this is expected behaviour, when connection is lost without unmounting - however it's irritating that this is the default (especially as, unlike for seemingly everyone else, I've got no way to ever mount the directory again because of that error, which survives restarting init.d/nfs AND rebooting the server?)
On a reddit thread on the topic, I've stumbled upon the recommendation to use systemd automount instead of autofs. I might give this a try if I can't get this to work any other way.
A hunch I've got just now - is it possible that fstab does not work because the mounted directory is not in /mnt/ but in my home directory instead?
Statistics: Posted by alvitali — 2024-04-09 22:40