@renzev@lemmy.world to linuxmemes@lemmy.worldEnglish • edit-22 months agoAverage systemd debatelemmy.worldimagemessage-square132fedilinkarrow-up1809arrow-down138
arrow-up1771arrow-down1imageAverage systemd debatelemmy.world@renzev@lemmy.world to linuxmemes@lemmy.worldEnglish • edit-22 months agomessage-square132fedilink
minus-square@InverseParallax@lemmy.worldlinkfedilinkEnglish8•2 months agoJesus, I mount everything manually from noauto, except root. If nfs isn’t available, I don’t want my system to hang, typing mount takes 2 seconds.
minus-squarePossibly linuxlinkfedilinkEnglish0•edit-22 months agoWouldn’t your NFS not mount in that case? Wouldn’t you want it to retry periodically? Also, what happens to your service when NFS isn’t available? Sounds like systemd mounts are better in this case (unless the device is non critical)
minus-square@InverseParallax@lemmy.worldlinkfedilinkEnglish4•2 months agoI mount it manually when I’m sure everything is up. The issue is, I use this workstation to bring up the rest of my network and servers if they’re down, can’t have a hard dependency on nfs if it’s job is to bring up nfs.
I’ve never seen it used in the wild
Jesus, I mount everything manually from noauto, except root.
If nfs isn’t available, I don’t want my system to hang, typing mount takes 2 seconds.
Wouldn’t your NFS not mount in that case? Wouldn’t you want it to retry periodically? Also, what happens to your service when NFS isn’t available?
Sounds like systemd mounts are better in this case (unless the device is non critical)
I mount it manually when I’m sure everything is up.
The issue is, I use this workstation to bring up the rest of my network and servers if they’re down, can’t have a hard dependency on nfs if it’s job is to bring up nfs.