Universal vs local time

[Mike Reinehr]

On Thursday 21 August 2003 09:36 pm, you wrote:
> Here is what I get with the various suggestions:
> hammer11:~# uname -a
> Linux hammer11 2.4.20 #1 Thu Jun 19 14:13:55 PDT 2003 i686 unknown unknown
> GNU/Linux
>
> hammer11:~# date
> Thu Aug 21 22:25:02 EDT 2003
>
> hammer11:~# date
> Thu Aug 21 22:25:20 EDT 2003
>
> hammer11:~# hwclock --show
> Thu Aug 21 22:25:31 2003  -0.431234 seconds
>
> hammer11:~# cat /etc/adjtime
> -0.000528 1061518802 0.000000
> 1061518802
> LOCAL
>
> My bios is set to local time. When I change it to UTC, the system sets it
> back to the local time either when starting up or shutting down.
> So, unless I want to get involved in those scripts (which I don't) this 
> box is staying on local time.

	You can use `hwclock` with and without the --utc option to query and/or set 
your hardware clock. I switched to Debian from COL a couple of months ago and 
one difference that I've noticed between the two is that when I'm shutting 
Debian down, it sets the hardware clock to whatever the software clock is, 
then, currently set to. This didn't happen with COL. I can't say which method 
is more prevalent, but it sounds like your distribution is resetting your 
hardware clock on shutdown. Again, with COL, there was a parameter buried 
somewhere in the startup scripts which attempted to determine whether your 
hardware clock was set to UTC or local, and then set the software clock 
accordingly. I have dug deep enough into Debian yet, to determine just how 
that's done.

mike

> Well, got THAT question answered. Onward.
>
> Joel
>
> _______________________________________________
> Linux-users mailing list
> Linux-users at linux-sxs.org
> Unsubscribe/Suspend/Etc ->
> http://www.linux-sxs.org/mailman/listinfo/linux-users

-- 
Debian 'Sarge': Registered Linux User #241964
----
"More laws, less justice." -- Marcus Tullius Ciceroca, 42 BC
--------