Let&#x27;s pull the last one from the list, because not only is it the most important, but it&#x27;s the one which best demonstrates the attitude the systemd maintainers have towards interoperability, standards, and security. Can systemd&#x27;s logger send to redis stores for aggregation? Can it email if there&#x27;s an issue? Can I pull windows events into the same aggregation systems? Is there an RFC for syslog&#x27;s file and network format?<p>These are all flaws in systemd with just one of those daemons you mentioned. Were I to get into init, I&#x27;d ask you about BSD-style rc files, which are tiny and very readable, as well as being shell scripts, so you can run more pre-execution tests to ensure your job will run correctly. With BSD atd and crond, I&#x27;d discuss how atd functionality has been merged in as a cron job. There are a lot of other solutions to sysv init than systemd. Unfortunately, the Linux monoculture sees bash as the only shell, sysv init as the only pre-systemd init, and the poorly configured rsyslogd distros ship with as the only syslog.