Hacker News Reader

Yeah this doesn’t even need the word “systemd” in it.

How else would it get upvoted to the frontpage, if not through the secret flamewar word?

Because it's written by an experienced and highly-respected academic systems administrator who's been continuously publishing his high-quality, ad-free blog for longer than Hacker News has been around.

Most people didn't do it before systemd made it the default. I imagine that's what triggered the problem for the author, and thus lead to the article.

It was so common to not restart that many services now have a "clear error logs on startup" policy.

Though systemd doesn't do it by default, you have to specify it on the service.

Interesting, pre-systemd the best practice everywhere I worked was to always restart. IME that's kind of the point of a supervisor in the first place.

You had to go out of your way to put your software under a supervisor. Most things were just launched by an init script and forgotten about.

Strangely back then the sky did not fall, automatic restarts were Windows’ solution to paper over its poor reliability.

I think we either started demanding more from our services or just accepting worse quality. And with the mainstream accepting silent restarts it’s only going to get worse.

Reply on news.ycombinator.com