Systemd requires every program that needs daemonize link libsystemd0
No, that’s only if you want the health check feature, so that systemd can distinguish between e.g. “The process is started” and “The HTTP server is bound and listening”
You can run hello world and a sleep() loop as a systemd daemon. You can run a Bash script as a systemd daemon.
I’m pretty sure that notification is also like 5 lines of code. You read an env var and that tells you a pipe to send a single character on.
You are not obligated to use libsystemd. And if you were you could certainly layer another init system inside of it
No, that’s only if you want the health check feature, so that systemd can distinguish between e.g. “The process is started” and “The HTTP server is bound and listening”
You can run hello world and a
sleep()
loop as a systemd daemon. You can run a Bash script as a systemd daemon.I’m pretty sure that notification is also like 5 lines of code. You read an env var and that tells you a pipe to send a single character on.
You are not obligated to use libsystemd. And if you were you could certainly layer another init system inside of it