this post was submitted on 20 Feb 2026
115 points (74.1% liked)

Technology

81653 readers
3995 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
115
systemd has been a complete, utter, unmitigated success (blog.tjll.net)
submitted 1 day ago by lemmydividebyzero@reddthat.com to c/technology@lemmy.world
79 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] cenzorrll@piefed.ca 7 points 1 day ago (1 children)

I'm not great at any init things, but systemd has made my home server stuff relatively seamless. I have two NASs that I mount, and my server starts up WAY faster than both of them, and I (stupidly) have one mount within the other. So I set requirements that nasB doesn't mount until nasA has, then docker doesn't start until after nasB is mounted. Works way better than going in after 5 minutes and remounting and restarting.

Of course, I did just double my previous storage on A, so I could migrate all of Bs stuff back. But that would require a small amount of effort.

[–] WhyJiffie@sh.itjust.works 1 points 22 hours ago (1 children)

what do you use as a prerequisite for the nas A mount? or does it iust keep trying in a loop?

[–] cenzorrll@piefed.ca 2 points 21 hours ago (1 children)

I have a wait-for-ping service that pings nas A, once it gets a successful response it tries to mount.

I lifted it from a time when I needed to ping my router because Debian had a network-online service bug. I adapted it to my nas because the network-online issue eventually got fixed and mounting my shares became the next biggest issue.

It seems like this person might have grabbed that same fix for what I eventually did because our files are...oddly almost exactly the same.

https://cweiske.de/tagebuch/systemd-wait-nfs.htm

[–] WhyJiffie@sh.itjust.works 1 points 16 hours ago* (last edited 16 hours ago) (1 children)

thanks!

do you perhaps also have a solution for hanging accesses to network mounts when the server is inaccessible?

[–] cenzorrll@piefed.ca 1 points 9 hours ago (1 children)

Do you mean a hang on boot when trying to mount? For that I use the nofail option in fstab. I also use the x-systemd.automount option so if something is not mounted for whatever reason, it tries to mount it when something attempts to access it.

[–] WhyJiffie@sh.itjust.works 1 points 5 hours ago

no, I mean the system has been up for a long time, but the server went down, and connection was lost