I want to run chrony on my servers for their smooth correction of system
time. I have a few questions, however.
1. Is chrony accurate on P4 and AMD chips? Is it really a useful
improvement
on ntpd? I remember from a few years ago that its developer used to have to
change his code every time a new CPU chip appeared.
2. Chrony doesn't like other programs interfering with its own control of
the clock, so I want to remove both ntpd and clock from the startup
process. This seems to cause a problem:
3. How do I substitute chrony for ntp in gentoo's startup scripts? I can
remove ntpd easily enough, but if I rc-update del clock it gets put back
into the boot run-level on shutting down. If I then move /etc/init.d/clock
out of the way and just touch a blank file in its place, I get this:
$ sudo /etc/init.d/chronyd restart
* Caching service dependencies ...
* Can't find service 'clock' needed by 'syslog-ng'; continuing...
[ ok ]
* Stopping chronyd ...
[ ok ]
* Starting chronyd ...
[ ok ]
It looks as though the baselayout team are assuming too much; or should I
just give in and revert to clock and ntpd? Perhaps it just isn't suitable
for Gentoo - it wouldn't be the first time that an ebuild had appeared for
a new package before it was ready.
--
Rgds
Peter
--
[email protected] mailing list
