🚀 go-pugleaf

In aus.computers.linux, on 29 Oct 1997 09:25:43 +1100
Nick Andrew <nick@zeta.org.au> wrote:
>In <633frp$iki$2@wyrm.its.uow.edu.au> gpc01@wraith.cs.uow.edu.au (Graham Philip Crowe) writes:
>
>>I found that the machine had to be on when the time changed over.
>
>Look for another solution. Local time is calculated on-the-fly according to
>the rules in the active timezone file (or your environment variable TZ) and
>"nothing happens" at the time of transition.

*nodnod* This is correct... *but* the reason why the machine had to be
on when the time changed over for him, is that he's probably got his
CMOS clock storing localtime, rather than UTC (GMT).

If that's the case, when he next reboots, the time will probably be out
of sync, unless he's writing out current time to the CMOS clock...

Anyway... I thought I'd better note that it's a *good* idea to make sure
your CMOS clock is set as UTC (note, this will unfortunately give Emperor
Bill's Software a hernia, since Emperor Bill uses the CMOS clock as
local time, instead of UTC, but since none of us have stuff belonging to
Emperor Bill on our computers... *grin*) so that time changes happen
nicely. :)

Later,

   David

-- 
Unico   Computer   Systems   Pty   Ltd
David Goh            Software Engineer
david@unico.com.au      (03) 9866 5688