[175483] in North American Network Operators' Group
Re: Linux: concerns over systemd [OT]
daemon@ATHENA.MIT.EDU (Chris Adams)
Wed Oct 22 16:57:34 2014
X-Original-To: nanog@nanog.org
Date: Wed, 22 Oct 2014 15:57:26 -0500
From: Chris Adams <cma@cmadams.net>
To: nanog@nanog.org
Mail-Followup-To: nanog@nanog.org
In-Reply-To: <25363.1414010923@turing-police.cc.vt.edu>
Errors-To: nanog-bounces@nanog.org
Once upon a time, Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> said:
> Actually, systemd 216 will cram systemd-timesyncd down your throat even
> if you had ntpd installed.
Yeah, I think a lot of the upset with systemd is not so much with the
core daemon that runs as PID 1, but with the massive scope creep that
the systemd project appears to have. Why should a project centered
around an init system start reimplementing system logging, network
management (and a DHCP client), clock management, etc.?
> Lennart's attitude was pretty much "why would anybody want to run ntpd
> when they have our SNTP implementation":
Wow, maybe because SNTP is inferior to an actual NTP daemon in just
about every way?
--
Chris Adams <cma@cmadams.net>
