Pro is free for personal use for up to 5 machines. Is there a problem with activating it?

That makes sense.

The last time we had a power issue and I was at my desktop I didn’t get any GUI notifications of the outage, so that’s a miss.

However the incessant beeping coming from every APC in the house was enough to tell me that stuff was about to go really sideways 😂 I was able to manually power down my desktop before the systemd stuff kicked in.

I’m not sure what you mean?

I’m certainly not saying systemd is the only way or best way to solve this problem, only that it does in fact work, despite the other many misgivings I have with it.

I’m also not sure whether you’re trying to turn this into a measuring contest, or why? My home setups are relatively rigorous for a residential setting, but they’re all based on the many many years I worked in data centers, mostly in Los Angeles which is notorious for poor power availability and stability.

That sucks!

I’m on Ubuntu, which I admit is not a popular option around here. But when my power goes out I use apcupsd and a network component to alert my attached or networked Ubuntu machines. When the power first goes out all of my non-essential machines automatically shut down gracefully. When the backup batteries get low enough (I have several separate APC units around the house) my essential machines also shut down automatically.

When the power comes back up one of my machines automatically powers up and runs a few checks before turning most of my other stuff back on.

I have very few power issues which last long enough for my batteries to run out, but when I do the only evidence is a few alerts and the fact that I have to log back into everything. All of my windows restore on my GUI machines, and no filesystem issues occur. It’s more seamless than when I ran Windows, granted that was 25 years ago.

I’m similarly not a fan of systemd, but for backup battery and power management it seems to do the trick.

I don’t expose anything to the internet other than the WireGuard endpoint.

This is the way

Tmux with a few custom key bindings is amazing. Kind of a learning curve, but not nearly as difficult as something like Vim.

I’m pretty sure I didn’t mess with systemd, though that would probably be the right way to handle it.

I was able to update a runtime config so if any storage wasn’t available it just halted the service. Then I created a short script I’d invoke manually which decrypted the luks drives and brought the dependent services up. I also added monitoring to alert me when the drives weren’t available for whatever reason.

I use separate disks for data storage and my OS. That way a headless system can boot and all the services like SSH can become available, and I can decrypt the data drives remotely.

When there’s an unexpected reboot I can still get into my system and decrypt remotely which is nice. I can also move the data storage disks to another system without too much hassle.

I did have to make sure some services were fault tolerant if an encrypted volume was unavailable when the OS booted. An example of this might be torrenting software, I needed to make sure the temporary storage was on an encrypted volume. The software had a sane fault mode when the final storage location was unavailable, but freaked out for some reason when the temp storage was missing.

Once set up the whole thing is pretty easy to manage.