

That’s not really systemd’s fault though.
Oh, but it is. Upstart and sysV will both assassinate everything after a point. This bullshit is entirely new, either by Systemd sucking, or Systemd allowing this shit (thus, sucking), where neither thing happened beforehand.
I admit I rage when it’s starting or stopping and can’t win for all the losing – especially because “startup time” was the the main (unfounded) feature on the banner they waved around.
I work with sysV and Systemd and shut each down on a. Regular basis, via tooling, for stuff like patching, so it’s often a horse-race to offline. The difference is often negligible, for new machines or established boxes with apps, and the main difference is sometimes Systemd fails its YOU HAD ONE job from time to intermittent time.
I work in a team where Unix and Linux is ~15 very experienced admins, so don’t fret over the skills and experience question or the scale question.

















I’m a senior xyz in one job and “the guy who’s been here 24 years” in the side gig. Half my job is asking “is that the best way to do that when it’s gonna also do this?” if I know it’s sub-optimal.