I had a different issue, and it relates to how chronyd works. Chronyd fails to work correctly if something outside its scope tinkers with the hardware clock and if, as on my system, I am not usually connected to the internet. My 6.2 system did not do a 'hwclock --systohc' when it shut down, but 7.3 does, and that tripped me up for a while, with rapidly diverging times.
I have not noticed any difficulties with hwclock itself. Cameron. > -----Original Message----- > From: Wolfgang Pfeiffer [mailto:[EMAIL PROTECTED]] > Sent: Saturday, 12 October 2002 04:15 > To: [EMAIL PROTECTED] > Subject: Broken hwclock? [was Re: Loosing Time] > > > On Oct 11, 2002, 11:45 (+1000) [EMAIL PROTECTED] wrote: > > > One problem with RH7.3 is that one needs to remove the command > > 'hwclock --systohc' from /etc/rc.d/init.d/halt otherwise it gets > > really confused. > > ... I'd be *extremely* careful with the hwclock version as > shipped with the Redhat util-linux package ... > -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
