systemd is the duct tape between GNU and Linux. Congrats, systemd just got one closer to making the entire userspace consist of a systemd pantheon.
I just realized, its the unholy trinity of computing: the Linux, the GNU and the systemd.
In more serious terms I'm glad to see Linux resembling OS X more and more. Launchd and systemd are like twins, separated at birth.
Wouldn't you agree that your stalking of systemd threads is a classic definition of "trolling", the same way as if a an enraged Plan 9 OS user constantly posted in all BSD threads on how much he hated *BSD?
The systemd opponents have lost each an every technical argument against systemd on Linux the last couple of years, mainly because they have been so totally ignorant what systemd is and what it actually does. Instead the system opponents, like you, rely on general hateful, but technically nonsense remarks, in a vain attempt to poison the systemd well. It may give you satisfaction to rant and rave against systemd, but it is exactly why you lose the discussions.
Think about that when BSD starts to develop its own counterpart to systemd: if you keep on the negative campaigning you will lose out on *BSD too. And yes, it is only a matter of time before the first BSD distro will attempt to clone systemd.
And on that last point, there are no "distros" of BSD. We have variants or forks. None of the 4 major variants want anything to do with systemd, if they want a process supervisor, they have OpenRC which doesn't use PID 1 and doesn't attempt to take over every daemon. Of course some are trying to port launchd to FreeBSD, but that will never be merged mainline. Maybe as a port, but even still, most FreeBSD users I know aren't into OS X.
I think to you all need to remember that you are "ambassadors" of your OS choice too. For some reason several BSD-users (and non-Linux users) tend to show up at these systemd threads where they apparently feel compelled by an inner need to spew out a rage rant against systemd, Linux, GNU and the GPL license too.
Not really sportive behaviour, and is bound to reflect badly back on all BSD users.
If this triggers, I even get a report (cron already emails stdout to root@localhost, then forwarded to a proper mailbox) with a notification dialog on my workstation (since my email client does that already). Absolutely nothing new was needed for this - no replacement pid1 or new initscripts, no replacement for cron, no replacement logging/notification mechanism in lieu of syslog and/or a properly-configured MTA on the host.Code:* * * * * root pgrep foo > /dev/null || service foo start
But it is not only about having many more features, it is also about scaling. These days a lot of Linux deployment is mass deployed servers: think 10.000 machines each with 100 processes, and we are talking one million processes that needs to be supervised. With all due respect for your solution, that may work very well for your work flow, your solution just won't scale very well. If eg. 10% of the processes are crashing due to a problem, the MTA's would send 10.000 emails per minute to all the System Admins. There are other, more advanced process management solutions around than your simple solution, but they don't come anywhere near the power of systemd either.
did they fix systemd terminating processes with kill at shutdown ?
hardware watchdog to supervise itself from hanging ?
audit is the tool to audit, an init is to init
a quantum leap indeed, by a Planck length that is