8 ms·
Wait, why is systemd running an ntp client?
by jimktrains2 11y ago
Wait, why is systemd running an ntp client?
- digi_owl 11y agoAnd a DNS client, and a cron replacement, and a inetd replacement, and a session/seat tracker, and soon to be a tty replacement.
- jryan49 11y agoIt's optional and has to be enabled... systemd is a suite of programs not just an init system...
- jimktrains2 11y agoWasn't that originally how dbus was and is now required?
- jryan49 11y agoSo you're telling me a dependency on an entire framework/server for IPC is comparable to a small NTP client...
- jimktrains2 11y agoNo, I'm telling you that once optional things have a way of becoming less optional.
- jryan49 11y agodbus is a server which applications use to talk to each other. Lots of applications started using it because it served their needs. dbus integration makes things go smoother since everybody else is already using it. The systemd NTP client is just another NTP client like any other you'd install. What could possibly make other parts of the system require that this specific service is running when it doesn't interact with applications?
- jryan49 11y agoThis seems to suggest you don't even need dbus daemon running to have things working: https://people.debian.org/~stapelberg/docs/systemd-dependencies.html https://people.debian.org/~stapelberg/docs/systemd-dependenc... just using the library doesn't seem bad to me...
- fixermark 11y agoZawinski's law of software envelopment perhaps? ("Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.")
- to3m 11y agoBecause, ultimately, PID 1 runs everything?
- digi_owl 11y agoNope. But everything depends on a specific binary running as pid1, something that is quite new in Linux history. Especially when thanks to dependencies on dependencies, desktops start requiring a specific binary as pid1.