The "Devuan" Debian fork and the fuss about systemd

Posted Dec 3, 2014 11:11 UTC (Wed) by anselm (subscriber, #2796)
In reply to: The "Devuan" Debian fork and the fuss about systemd by mgb
Parent article: The "Devuan" Debian fork

From a sysadmin's point of view, systemd is providing *incorrect* answers - megabytes of config files with hundreds of poorly documented options, logging bottlenecks, incorrect DNS results, and time jumps.

You must be talking about a different systemd than what most people are using. Most of the points you raise have been debunked over and over again here and elsewhere.

As far as systemd's time synchronisation service is concerned, there are two points worth noting:

systemd-timesyncd supports SNTP, which is a simplified version of NTP. This means that you should use it in a context where you have a set of local time servers that run a full-blown NTP server implementation, and you don't want to run an NTP server on every single machine. If you distribute the names of your NTP servers by DHCP, systemd-timesyncd does not require any local configuration at all.
Systemd makes it easy to deploy a different NTP implementation such as chrony or ntpd, which are safer on standalone machines without a local time server elsewhere on the LAN. This is documented in systemd's timedatectl(1) man page.

What fraction of RHEL sysadmins have actually bought into the hype and deployed systemd in production servers?

Those who have upgraded to RHEL 7, presumably.