you can stop and start it via systemctl and systemd is going to make mounts for fstab entries automatically, I just put local drives in my fstab so that way I can copy mount files between machines
With these systemd mount files I don't need to touch the fstab, I can use ansible to copy the file, enable the service then start it. I can also have other services like Docker, Jellyfin or whatever to depend on that service. If the nfs share can't be mounted then systemd won't try to start docker.
With these systemd mount files I don't need to touch the fstab, I can use ansible to copy the file, enable the service then start it. I can also have other services like Docker, Jellyfin or whatever to depend on that service. If the nfs share can't be mounted then systemd won't try to start docker.
So you can easily start and stop it as a service and you get your logging easily accessible via journalctl as a unit. But practically speaking there's not much difference.
Yeap! You can even make an automount unit too! That way it’s mounted on demand! Makes life sooo much easier. I even do it for my external drives I use for backups
Oh that's easy! I have this friendly multi-page PDF that assumes you have an active directory domain already (god rest your soul if you're raw dogging kerberos and ldap raw) that walks you through the instructions step by step and...
I'll probably switch to simple script, since I don't like the idea of my laptop shouting my NAS access credentials into any available random network on startup.
You may want to consider adding nofail and x-systemd.device-timeout opinions on the mount as well if the NFS isn't critical to the device booting, and speed up your boot process a bit.