Hacker News new | past | comments | ask | show | jobs | submit
bayindirh | on: A live tree of systemd jobs on the boot console
Not the OP, but to provide a short perspective:

    - Too many parts.
    - Doing too many things, sometimes poorly.
    - Fights with other services, no graceful fallback & logging (i.e. aggressive).
    - As a result, unnecessarily complex, brittle and fragile.
    - Harder to secure (at code level) than simpler tools.
    - Project is too aggressive and want to replace any and every service.
    - Sometimes break in unexpected ways.
    - Not faster than Parallel Sys-V.
We can discuss these. I'm not the one who wants flame wars.
jimis | parent | next
+ Harder to debug/trace than initscripts.
loading story #50465256
torcete | parent | next
I reckon using cron vs systemd timers is a good example of some of the points above.
fhn | root | parent | next
cron does not have millisecond accuracy which is important in some use cases.
jeffrallen | root | parent
Oh my god yes. Systems timers are doubleplus ungood.
dofm | root | parent
Unless you want to run something every thirty seconds.
loading story #50467331
loading story #50465931
preisschild | parent | next
It has the exact right amount of parts. A modern Operating system just has a lot more to cover than 1970's Unix...

I can remember having to deal with SysVinit and thank god for Poettering and all the other systemd maintainers for bringing the Linux ecosystem to the 21st century

loading story #50465365
loading story #50465297
loading story #50465737
origini | parent
I'm using systemd for ages, never had a single issue at all with it.

But do you run systemd and complain or why do you even hate it?

its linux right, if a linux distribution decides to use it, its not systemds fault to be used and if you use it and don't take the time and effort to have it your way, you shouldn't complain either?

loading story #50465584
mpvjs | root | parent | next
I had been using debian from potato to jessie beta, the first issue that was random (unlike all previous issues with debian that were consistent across reboots and often across architectures) was boot in jessie beta. Did not even know what systemd was, so i thought debian went down in quality as I was used to have even sid behave well. BTW the first issue who hit me in production when tests were all good was a pulseaudio glitch...
kodoman | root | parent
Wait till you do have an issue or even just want to disable one of the 'helpful closely coupled' services something works to better fit what ever you doing or for security/reliability reasons (D-Bus is a great example for me).

It's difficult to avoid systemd at this point and it's not because it's the best technical solution for all use cases in the same way that modern windows is a complete shit show but still everywhere.

My question would be what does systemd do that is not possible outside of openrc and launching what ever daemons you want for the tasks you want or combining it with what ever programs you want to do things like sand-boxing or containerization? Not saying openrc is a panacea but systemd is definitely not either and for many systems is just plain annoying, I can consed for people who want a normal desktop (plug and play distro experiences) experience it can provide that.

loading story #50466295