Am 28.07.2014 18:47, schrieb Rich Freeman: > Anybody have a decent comparison of timedated vs ntpd or anything else > for that matter? > > Running ntpd isn't hard at all, so I'm not really sure why I'd want to > switch. At the very least I'd want to ensure that the replacement > covers the basics. > > I am running networkd and I'm very happy with it. Setting it up for > dhcp-only is brain-dead simple, and I have it serving up a bridge for > containers/kvm with fairly little trouble as well.
AFAI understand it the systemd-timedated.service helps setting clock and time-related settings ... and if you use it to enable NTP syncing, systemd-timesyncd.service will actually take over the part of syncing with ntp servers. I also preferred chrony over ntp for the last year or so. Better with laptops etc. and quicker to correct time when there is large offset. What I haven't yet fully understood: daemons like chrony bring a specific settings file for systemd-environments, in this case: /usr/lib/systemd/ntp-units.d/50-chrony.list (saying "chronyd.service") In the same directory I see 90-systemd.list (saying "systemd-timesyncd.service"). As far as I understand this: if other ntp-software is installed, systemd-timedated.service uses the ntp-unit with higher priority (in my current case chronyd.service) for ntp-syncing. So you may use the systemd-timedated.service to do your settings and in the same setup let it use another ntp-daemon to actually do the syncing behind the curtains. Generalized interface with choice --- nice, isn't it? ;-) but maybe I misunderstand. Stefan
