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.
I’ve had Linux problems before too when I was still trying to use it and I’d post the issues on like 4-5 different active forums and never get anything to solve it. So posting a meme acting like something is impossible seems like an amazing way to get instant help from the Linux knights.
Linux user here, this would have been super helpful to me in the past. I don’t think it’s that the world is full of master Linux users that don’t post, it’s that new people need more help and have more questions.
Fwiw, as someone also recently new to Linux, I thought this captured part of the experience brilliantly, and without malice.
Of course op probably went on to google (and find) the answer, so I agree with you that getting the answer with this post was probably not the point. But it’s a quality shitpost, and I endorse it! 😀
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
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.
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…
Here’s how to mount an nfs share:
#cat /etc/systemd/system/mnt.data.mount [Unit] Description=nfs mount script [Mount] What=192.168.0.30:/mnt/tank/Media Where=/mnt/data Type=nfs4 [Install] WantedBy=remote-fs.targetI’ve always mounted network shares in fstab, what’s the benefit to doing it with systemd?
(Also, for those of you learning, this method only works on systemd-based distros)
Removed by mod
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.
Systemd can retry mounting based on the restart policy in case you have an interruption.
deleted by creator
I’ve had Linux problems before too when I was still trying to use it and I’d post the issues on like 4-5 different active forums and never get anything to solve it. So posting a meme acting like something is impossible seems like an amazing way to get instant help from the Linux knights.
and btw, the i never though about monting using systemd, no i came for the memes, and learned something
Linux user here, this would have been super helpful to me in the past. I don’t think it’s that the world is full of master Linux users that don’t post, it’s that new people need more help and have more questions.
Fwiw, as someone also recently new to Linux, I thought this captured part of the experience brilliantly, and without malice.
Of course op probably went on to google (and find) the answer, so I agree with you that getting the answer with this post was probably not the point. But it’s a quality shitpost, and I endorse it! 😀
Removed by mod
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.
Removed by mod
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
Meanwhile I found a solution using fstab.
What’s the advantage of using a systemd script?
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.
How would you do this with fstab? (Working with an smb share which I’m assuming is standard)
I described what I did here.
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.
That sounds useful, thank you very much.
An now explain how to setup Kerberos
No idea, I don’t use Kerberos.
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…
mount.nfs4: access denied by serverWhat=Kerberos Where=pam