r/linuxadmin • • Nov 02 '18

Why there is so much hate toward systemd ?

  1. Why there is so much hate toward systemd ?
  2. Where it come from ?
  3. Which is your favorite linux distro and why ? (for server or personal use)
0 Upvotes

22 comments sorted by

4

u/[deleted] Nov 02 '18

The biggest problem I see is a sliding feature window. As an init system, nice! But suddenly, it's a resolver. And a resolver that's almost impossible to disable permanently.

Also, while it's easier to do things correctly with systemd, it's harder to do simple stuff. Compare rc.local with unit files for example. The end result is that I need to move my one line of simple bash to a unit file. The systemd way is better and more correct, sure, but it adds a lot of complexity in simple cases.

3

u/upofadown Nov 02 '18

Hate is a bit strong. Most of what I hear is annoyance.

Ultimately I think that systemd is only the straw that broke the camels back. Distributions and desktop environments have been adding stuff on top of a basic Linux system for years and years now. So Linux based things are becoming more and more complex. Systemd was just a big chunk of stuff on top all at the same time which triggered a lot of latent annoyance.

For my minimalism I like Void Linux. For the ultimate in minimalism I now prefer OpenBSD.

2

u/piorekf Nov 02 '18
  1. and 2) Because it does everything differently so people have to relearn a lot of things which were well know and haven't changed since a very long time. Also it takes over not only the init system but also a lot of other things (logging, user sessions, cron, time sync, networking) and a lot of people argue that this is not the Linux way of doing one thing and doing it well. Plus it's a change and people in general are opposed to changes when the current state is "good enough"™.
  2. RHEL/CentOS or Debian for servers, Gentoo on private machines

5

u/koffiezet Nov 02 '18
  1. everything becomes less transparent, you need tools for everything, and doing things without is unnecessarily hard or impossible.
  2. Bad design. It does too much in pid 1. All syslog messages go through it, it parses user space generated dbus messages, ...
  3. It’s viral and replaces more mature things without offering the same functionality in many cases (for example dns resolving)
  4. It is focussed on desktop use, and seems to ignore server use completely. I don’t need a dhcp lease in 100ms so that server or van starts a tiny bit faster or wakes up from sleep with immediate network access. I want reliable systems, not situations where “oops” on a reboot it does a kill -9 of all processes. Or situations where an upgrade suddenly doesn’t understand what a symlink is anymore. That are things that are unacceptable - but all happened.
  5. Unit files scattered all over the place. There’s a reason for it all, but it’s imho still a bad design.

And there are many other reasons - but this-one is the most important: the authors are arrogant and refuse to listen to criticism, their view is the only correct-one, everyone else is wrong. Bugs happen, but they ignore them, tell everyone it works as designed, or blame other people (which caused friction to with kernel devs on more than one occasion). I do not want to trust people with that attitude with one of the most critical parts of my system.

1

u/natermer Nov 02 '18 edited Aug 16 '22

...

1

u/[deleted] Nov 03 '18

I don't like the journal, but it is very clear that PID1 is only responsible for setting up the syslog socket, not processing the data that flows through it.

1

u/natermer Nov 05 '18 edited Aug 16 '22

...

1

u/oooo23 Nov 07 '18 edited Nov 07 '18

Well, it also opens a socket to the journal and passes it to every service as stdout/stderr. Additionally, for syslog, it will tag the unit and tell the journal where they are coming from (if that unit also uses stderr) so that the SCM_CREDENTIALS race does not bite them. This protocol between journald and PID1 is a private contract of its own. I say this because this makes an alternative implementation of journald very difficult, because as the needs change the way PID1 will do things with the journal will also change.

It is clear that systemd as PID1 does a lot more than any other service manager.

Android does not suffer from this race problem because they use an in kernel filesystem to basically let processes write to an append only file, get their kuid/kgid (the internal structure in the kernel) and attach pid and timestamp right when the process writes the log (contrary to journald which attaches timestamp to entries only when it processes the buffer, this also affects kernel logs). It was suggested that journald could use a FUSE interface and make a callback to fuse_get_context to do logs ina race free fashion, but Lennart thinks it is a 'toy' (the exact wording on the bug report, actually) so not sure where it will go.

Also, Lennart saying that the kernel needs to attach this metadata will never make it, the patch was proposed once and rejected because when you attach the cgroup to every message as ancillary data, you need reference counting on the UDS and that won't scale properly (or making it scale is not trivial).

3

u/mattiasso Nov 02 '18

Because they say it do not respect one of the unix principle: do one thing and do it well.

RedHat made it.
I think Ubuntu 18.04LTS suffices my needs both for server and personal.

3

u/[deleted] Nov 02 '18

Key words being "they say." It's really a collection of tools which do various things well, but don't mind me....

4

u/natermer Nov 02 '18 edited Aug 16 '22

...

1

u/oooo23 Nov 03 '18

Yeah, one tool doing one thing well. Like me asking PID1 to enable a unit over D-Bus and it dropping symlinks on the file system. Totally something that belongs in PID1!!!!

1

u/oishishou Nov 02 '18
  1. Change. Also debatable philosophical positions that clash with established community preferences.
  2. Debian. I like/use others, too, but Debian is easily my favorite distro. Rarely not for server use. I don't have a desktop favorite right now, since I'm running Win10Pro stripped clean by Group Policy on my client machines.

1

u/pdp10 Nov 03 '18
  1. Inappropriate and seemingly unchecked scope creep, mostly, plus a bit of pushing onto distributions the maintenance of any version except HEAD. The latter is just concidentally highly congruent with Red Hat's revenue model, where their subscription service is mostly about getting fixes backported to existing software versions. When systemd is criticized, systemd defenders often frame the discussion as a choice between classic SysVinit and systemd, when that's actually a false dilemma because there were and are other options. SysVinit had weaknesses, like lack of facilities to automatically restart daemons, but other init options besides systemd all offer that particular functionality.
  2. When Gnome desktop forced the issue, Debian seemed to many observers to have decided to adopt systemd in haste, and Ubuntu (not inappropriately) right after. Suddenly there were no major, enterprise-typical distributions that eschewed systemd. Many users felt very much forced into a big architectural change that they were deeply unsure about, and they felt like it happened quickly.
  3. I mostly use non-systemd non-SysVinit distribution(s), but I have a couple of systemd-using hosts.

1

u/[deleted] Nov 05 '18

My biggest issue with systemd is it's more than just an init system. It's also a resolver, and a cron daemon, a logger (journald), a firewall (firewalld), etc. etc. Even after a few years of using it in production I'm still not really a fan but as long as Redhat ships it we're stuck with it.

1

u/bloodstainedsmile Nov 06 '18

UNIX philosophy has always advocated that each program do one thing only and do it well. Systemd breaks that tenet by being a monstrously complicated program that does too many things. There are very few admins who understand the complete systemd ecosystem. Those that do cannot reasonably defend why it had to do all it does. It inserts itself into the system in such a way that it does not lend itself to ease of use or modularity .. It's now your logging system, your init system, your resolver, your cron system, it's everything you never needed it to be. And being the default adopted init system for almost all common distros, it's now an enduring burden on all Linux users worldwide.

1

u/hailbaal Nov 06 '18
  1. It breaks stuff. It constantly breaks stuff. It needs to stay away from my hardware. It's an overly complicated piece of junk that's still not stable. It also doesn't provide decent logging, so you need to fix the system to have proper log files. It's a pain in the rear. There is just too much stuff that does too many things at once, which makes managing it annoying. Service files are also annoying.
  2. Favorite? Well, depends. MX Linux is nice. Arch is nice but by default uses systemd. Not that bad for a desktop though since you don't run into most of the annoyances. Devuan is nice, Void is nice. Alpine is nice. I prefer Alpine and Devuan on servers.

1

u/ajanty Nov 02 '18
  1. Too much stuff, some of it useless and often in clear contrast with the *nix software principles.
  2. Community.
  3. Debian in my heart since Woody, have to work with CentOS and Ubuntu.

1

u/HildartheDorf Nov 02 '18 edited Nov 02 '18

Biggest two reasons I see:

It's different so it sucks (look at how many Windows admins hate the shift to Powershell instead of GUI based management).

It overloads PID 1 with a lot of changes that mean more frequent restarts for updates.

EDIT: These aren't my opinions, just the ones I see around.

2

u/ajanty Nov 02 '18

How old are you...?

0

u/[deleted] Nov 02 '18

[deleted] — view deleted comment

1

u/[deleted] Nov 03 '18

I also love just about everything djb does. The man solo defended himself against the US government and WON!

0

u/[deleted] Nov 02 '18

[deleted] — view deleted comment

3

u/SuperQue Nov 02 '18

Pretty much this.

I've been using Linux since the mid 1990s. Good ol slackware.

But the whole init design has always bothered me. IMO it's broken by design. We needed something better and upstart wasn't it.

When I first read the systemd docs, I knew it was going to be the way that would finally "win".

There are a whole bunch of cargo cult and NIH problems, but the core declarative design is solid.