> I understand some of the systemd criticism, but I don't at all understand why you want something else to manage your processes than the process management sys

> I understand some of the systemd criticism, but I don't at all understand why you want something else to manage your processes than the process management system (which is basically always the init system)? Perhaps you don't understand one of the fundamental, philosophical criticisms, which is that it violates the Unix tenet of "do one thing and one thing well". Timing, and scheduling are difficult and (arguably, of course), deserve their own, separate utility. Cron isn't a process manager, any more than and interactive shell [1]. It just starts processes (and passes output to a local email client, though that's, understandably, brittle). I wouldn't object to moving the process-starting functionality out of cron and leaving it with only the ability to tell init to "start job named XYZ", but I do object to just integrating its core competency of scheduling into that init. [1] Arguably less than, considering modern shells' job control and signal facilities