| > When I want to write a script that runs on startup, I expect that I can just put (or link) it in some directory where the scripts are that get started on startup. Or that there is one main script that calls all scripts that are intended to be startet on startup. AFAIK, systemd is compatible with sysv init scripts. > I do not want to write a "service" that has some "only run once and then discard" flag or whatever. Why? Writing one isn't so complicated. > When I want to look at logs, I want to use the tools I like. less, grep, tail etc. I do not want to dabble with some binary format and its tooling. Well, nothing prevents you from piping output from journalctl to whichever tool you prefer. In fact, people do it all the time. > When I want to start or stop a service, I want to call a script that does that. A script which I can look at and see what it does. Like /etc/init.d/apache2. I do not want to execute some magic command like "service apache start" which I have to guess or look up and which gives me no clue about what it does. I don't see how sysv init is any better than systemd in this regard. You'd still have to look at indidual scripts to see what it does. It's not like systemd hides the contents of the service files. |