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.target
I’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)
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.
Kinda interested now, why would you use systemd script for this instead of fstab ?
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.
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! 😀
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)
