From anti-systemd to pro-systemd in the shortest time

I was trying to show rather fundamental ways in the sysv example script can return false or misleading results or do something completely unexpected. Of course each and every one of those has a workaround. Knowing all those hacks is competence in a sense. It is also time wasted which could actually be put to better use than fighting around deficiencies in the basic building blocks of the OS. I don't want to "troubleshoot" anything, if the service manager already has the necessary information. I don't want to check if the daemon I started is actually running. I think we can agree that having a system which handles OOM conditions reasonably is better than always throwing "enough" RAM at the problem.