2 ms·

Yes, these are also reasons I dislike systemd. Also, one of the original selling points of systemd was "It will reduce boot times significantly!" ... And then i

Yes, these are also reasons I dislike systemd. Also, one of the original selling points of systemd was "It will reduce boot times significantly!" ... And then it ends up that systemd is actually slower to boot than any of the other ones out there.

dijit 10y ago
it can be with the process timeout weirdness, where init used to be 'fire and forget' so if something didn't respond it would carry on systemd actually depends on the output so will sleep for 180seconds or so. But honestly, even an extra 30s booting a server is nothing, I don't give a shit about boot times on my servers.. I care about what order my services are started in- my servers should be 100% reproducable otherwise you could have bugs that never get found except in 1% of cases. And since it's turtles all the way down 1% of one system can be a lot of problems in a 2,000,000 server architecture. So "Fast boot" in the way systemd achieves it is not beneficial for me.
justinsaccount 10y ago
> Also, one of the original selling points of systemd was "It will reduce boot times significantly!" It was not. http://0pointer.de/blog/projects/the-biggest-myths.html http://0pointer.de/blog/projects/the-biggest-myths.html Myth: systemd is about speed.
- rkeene2 10y ago
  http://0pointer.de/blog/projects/systemd.html http://0pointer.de/blog/projects/systemd.html The original blog post introducing systemd on 30-APR-2010. The first points that it details regarding the thesis of systemd is that it is a good init system, and a good init system is fast, and that SysV init is not fast. The first time it begins talking about things a service management system should be interested in is about half-way through with "Keeping Track of Processes". It spends roughly the rest of the document on important service management things, but to dismiss the idea that "systemd is about speed" is a myth is too much. systemd IS about speed of booting -- during the development there were flame graphs showing how doing all this in parallel you could make the system boot really really fast. A lot of time was spent making the boot process with systemd minimal, or speedy. Personally I'd prefer a less speedy service management system that didn't open listening sockets for my daemons so that it could deal with starting services out-of-order... to make the boot occur in a more parallel fashion... to make the boot faster.
- wott 10y ago
  No, that's revisionism, Poettering rewriting history.

dijit 10y ago

it can be with the process timeout weirdness, where init used to be 'fire and forget' so if something didn't respond it would carry on systemd actually depends on the output so will sleep for 180seconds or so. But honestly, even an extra 30s booting a server is nothing, I don't give a shit about boot times on my servers.. I care about what order my services are started in- my servers should be 100% reproducable otherwise you could have bugs that never get found except in 1% of cases. And since it's turtles all the way down 1% of one system can be a lot of problems in a 2,000,000 server architecture. So "Fast boot" in the way systemd achieves it is not beneficial for me.

justinsaccount 10y ago

> Also, one of the original selling points of systemd was "It will reduce boot times significantly!" It was not. http://0pointer.de/blog/projects/the-biggest-myths.html http://0pointer.de/blog/projects/the-biggest-myths.html Myth: systemd is about speed.

rkeene2 10y ago
http://0pointer.de/blog/projects/systemd.html http://0pointer.de/blog/projects/systemd.html The original blog post introducing systemd on 30-APR-2010. The first points that it details regarding the thesis of systemd is that it is a good init system, and a good init system is fast, and that SysV init is not fast. The first time it begins talking about things a service management system should be interested in is about half-way through with "Keeping Track of Processes". It spends roughly the rest of the document on important service management things, but to dismiss the idea that "systemd is about speed" is a myth is too much. systemd IS about speed of booting -- during the development there were flame graphs showing how doing all this in parallel you could make the system boot really really fast. A lot of time was spent making the boot process with systemd minimal, or speedy. Personally I'd prefer a less speedy service management system that didn't open listening sockets for my daemons so that it could deal with starting services out-of-order... to make the boot occur in a more parallel fashion... to make the boot faster.
wott 10y ago
No, that's revisionism, Poettering rewriting history.