Public SourceMage Discussion List

[Casey Harkins <charkins AT upl.cs.wisc.edu>]

I had this problem as well and with the help of #sourcemage tracked it
down to the hwclock.sh init script needing NEEDS="+local_fs" when the
real time clock driver is built as a module. The fix was pushed into
all grimoires, so re-casting util-linux should fix it for ya.

This has actually been happening for a while, but I never bothered to sit
down and figure it out until last week.

Now I'm experiencing some un-related time issues on another machine! The
system and hardware clocks match and are correctly showing localtime
(hwclock stored in UTC), but fcron jobs show the time being adjusted for
localtime a second time, so they are off.

-casey


On Fri, 31 Oct 2003, Robin Sheat wrote:

> On Thu, Oct 30, 2003 at 11:05:30AM +0100, Arwed von Merkatz wrote:
> > You may want to check /etc/sysconfig/hwclock and set UTC correctly. If
> > your hardware clock stores the localtime directly (needed for some
> > broken OS), set UTC=no and it should set the time correctly.
> Yeah, the hw clock is local, as I used to dual-boot to windows on this box. 
> I should
> probably look into changing it to UTC now windows is not used. BTW there 
> was no
> /etc/sysconfig/hwclock, so I created it. Probably no problem there. (haven't
> rebooted yet, but my computer is for some reason unstable lately, so it may 
> not be
> long.)
>
> --
> Robin <robin AT kallisti.net.nz>                 JabberID: <eythian AT jabber.org>
>
> Hostes alienigeni me abduxerunt. Qui annus est?
>
> PGP Key 0x776DB663 Fingerprint=DD10 5C62 1E29 A385 9866 0853 CD38 E07A 776D 
> B663
>