4 ms·
And that seems to be the eternal issue. Poettering seems to come at this not from an admin perspective but from a developer perspective. And with RH shifting th
by digi_owl 12y ago
And that seems to be the eternal issue. Poettering seems to come at this not from an admin perspective but from a developer perspective. And with RH shifting their focus more and more towards cloud computing, so is systemd.
And in cloud computing the admins are not kings, but peons.
Peons tilling the cattle (server) farm of 100s of servers, each running any number of VM instances. If one or more of those instances go down, new ones are spun back up.
And you see this attitude within systemd. If a daemons crashes you don't leave it down and try to figure out why it crashes. Instead systemd will simply restart any daemon it finds not to be running when it should.
Basically this is not uptime by way of applying carefully measured and maintained administration. This is uptime by machinegun.
It is what allows anyone with some grasp of php to rent server time on a amorphous blob like the Amazon EC2 and spin up the next Twitter or Facebook.
No need to optimize for or maintain the hardware. If the current load is too much, wave your credit card and have 1000 fresh instances behind the the load balancer, courtesy of Amazon or RH.
Datenwolf is demonstrating the kind of exasperation that have in the past driven people to look for alternatives to Windows. They thought they had found the promised land in Linux, but now the blight is coming over the walls and taking up residence even here.