Index: [Article Count Order] [Thread]

Date:  Tue, 15 Apr 2008 08:35:27 -0500
From:  "Gerald Waugh" <gwaugh (at mark) frontstreetnetworks.com>
Subject:  [coba-e:12588] Re: Different Clock Times
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <017001c89efd$94fafb90$0101a8c0@systemax>
In-Reply-To:  <412329.26280.qm (at mark) web65616.mail.ac4.yahoo.com>
X-Mail-Count: 12588

Dan wrote;
> 
> What's strange is, I have had such a setting since before the 
> last reboot
> of the server.
> 
> -- 
Try running these commands,
date
hwclock --utc
hwclock --localtime
hwclock
hwclock --debug

examples from one of my servers...
[root@fsn3 ~]# date
Tue Apr 15 08:33:48 CDT 2008
[root@fsn3 ~]# hwclock --utc
Tue 15 Apr 2008 03:33:49 AM CDT  -0.651963 seconds
[root@fsn3 ~]# hwclock --localtime
Tue 15 Apr 2008 08:33:50 AM CDT  -0.989847 seconds
[root@fsn3 ~]# hwclock
Tue 15 Apr 2008 08:33:51 AM CDT  -0.962861 seconds
[root@fsn3 ~]# hwclock --debug
hwclock from util-linux-2.12a
Using /dev/rtc interface to clock.
Last drift adjustment done at 1207767802 seconds after 1969
Last calibration done at 1207767802 seconds after 1969
Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2008/04/15 08:33:52
Hw clock time : 2008/04/15 08:33:52 = 1208266432 seconds since 1969
Tue 15 Apr 2008 08:33:52 AM CDT  -0.989559 seconds

-
Gerald Waugh
http://frontstreetnetworks.com
Front Street Networks
4604 Fern Ave
Shreveport, LA 71105-3118
United States of America
Phone: +1 318-401-0428