That’s all handled with adding the x-systemd.automount option to my fstab entry. If it disconnects it’s unmounted, when it’s available again it mounts when something tries to access it.
I have occasionally needed to restart some services if they didn’t like getting disconnected, but as far as mounting goes it’s handled pretty smoothly with that option.
I brought my 2003 laptop back to life for shits and giggles recently. It’s made me realize how bloated software has become. It’s still just as usable as it was 20 years ago when you remove all the fancy crap and use programs designed for tasks rather than living in a web browser. Sure its not fast, but once I replaced the spinning drive with an ssd, it became pretty damn usable in a modern day scenario. I really thought I would just upgrade as far as I could for fun, then slap an old archived distro on there from my college days for some good old PTSD/nostalgia. But it’s actually usable so I occasionally pull it out and do stuff on it. I’m ready to slap jaunty jackalope on it and relive going to my uni’s library to write a 10 page research paper thats due the next day, but it’s still ready to rock in modern times.
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.
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.
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.
The indicator turns into a “manager’s special”, no need to pay an employee to slap them on anymore
This happened last year. This isn’t a new occurrence, I can’t see anything referencing anything new except maybe the lawsuits.
Edit: never mind, I just skimmed, saw lawsuits section, and checked sources, there aren’t even any lawsuits referenced in this
This is the event that happened last year.
I’m imagining you’re actually using the vintage computer and its just screaming at having been connected to the internet