On Tue, 24 Dec 2002, Bob Nielsen wrote: > On Tue, Dec 24, 2002 at 09:44:23AM -0800, Bill Moseley wrote: > > On Wed, 25 Dec 2002, Rob Weir wrote: > > > > > On Tue, Dec 24, 2002 at 06:36:22AM -0800, Bill Moseley wrote: > > > > On 24 Dec 2002, John Hasler wrote: > > > > > > > > > Bill Moseley writes: > > > > > > I just don't think it unreasonable that there could be periods of time > > > > > > when ntp can't connect to the remote hosts -- and that should not stop > > > > > > ntp. > > > > > > > > > > Chrony is designed to work with intermittent connections. > > > > > > > > Any idea why it conflicts with ntpdate? Installing it remvoed ntpdate. > > > > ntp didn't conflict with ntpdate. > > > > > > No idea...chrony is a lot smarter than ntpdate though; it gradually > > > moves your clock back and forth so that running apps don't get confused, > > > as well as tracking how inaccurate your hardware RTC is, and fixing it > > > while it drifts. Overall, a very cool tool. > > > > Maybe I missed this in the docs, but I didn't see that it updates the > > hwclock during normal execution. It can be made to update the hwclock > > (the example they give is in a ppp-down.d script), but in my case the > > machine boots and ppp comes up and the only time it goes down has been a > > power failure. So pp-down.d scripts are not called. > > > > Did I miss something? > > As John Hasler recently pointed out, add 'trimrtc' to > /etc/chrony/chrony.conf.
trimrtc is a command for chronyc. It's not listed in the docs as a valid chrony.conf option. If I try to add it to chrony.conf I get: Dec 24 13:33:20 burn chronyd[1804]: Line 70 in configuration file [/etc/chrony/chrony.conf] contains invalid command I suppose it could be given as a command to chronyc in a cron script. Running chrony package 1.14-7 -- Bill Moseley [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
