As much as I disliked systemd initially, I hate working with hacky shell script based sys-v-init. Recently I needed a short daemon to monitor network connectivity of my backup server. I wrote a py program to do that and instead of making it a daemon with backgrounding, logging, writing sysv scripts for it etc, I wrote a 10 line systemd service definition. Anything it prints to stdout+stderr gets logged, it is auto-restarted, memory limits, enabled on startup etc. SIMPLE.

followup:

With systemd, its functionality is config driven fixed functions and any extensibility often handled by small simple shell scripts at the edge. The core is predictable, FINALLY bug-free, and very powerful. This rainy weekend I decided to spend some time upgrading my machines from: GNU/Debian 12.1 to 12.4, another from 11.6 to 12.4 and my main home server from 10.13 to 12.4 :) Still need to migrate ifupdown to dhcpcd, iptables to nft and xorg to wayland :) Times sure do change.

followup:

@ghast point-taken, few things are, let me rephrase, “reasonably/usably bug free”.

followup:

@ghast what were the symptoms and the actions leading up to systemd NON-init ? just curious, I believe it.