Hacker News Reader

> On the one hand you have the traditional server/sysadmin thinking about uptime and stability.

For sysadmins, boot times are getting increasingly more important. We're getting to the point where we can spin up a new VM in <100ms, thanks to (in part) systemd. This doesn't matter if you've got a few servers in a rack, but it does if you're spinning up thousands of VMs.

View on HN

And for every one that has 1000 VMs to wrangle, there are 1000+ that have a couple of servers in a rack.

Nice thing is - systemd works well for both.

I have yet to see any evidence of that, as systemd seems liable to blow up at the oddest of moments (thus making it unsuitable for a long term server).

It will rearrange the boot sequence on a whim, it will keel over if dbus does, it will fail to boot on the smallest of unit errors (to the point of providing no means of remote access no less).

It may work in a cattle ranch, and it may work on someones laptop, but it damn sure does not work in a rack.

Reply on news.ycombinator.com