I installed CentOS 5 on a server today (wiping clean the drive which had 4.4 on it). During installation I picked the correct timezone, location and all. Yet, upon booting the machine, it seems to think that it's 6 hours earlier than it really is.
The BIOS has the correct time and date on it.
/etc/locatime was originally what /usr/share/zoneinfo/America/Denver would've been. I removed it and symlinked it instead thinking it might change things - it didn't.
Right now, 'date' tells me:
[1] 13:21:12 <root@bigbertha:~> date Sat Apr 14 13:21:13 MDT 2007
But it's actually 19:21...
So, uh, what's going on? Why is the time so off? Under CentOS 4, the time was just fine. Something happened in 5.
On 4/14/07, Ashley M. Kirchner ashley@pcraft.com wrote:
I installed CentOS 5 on a server today (wiping clean the drive whichhad 4.4 on it). During installation I picked the correct timezone, location and all. Yet, upon booting the machine, it seems to think that it's 6 hours earlier than it really is.
One to add to the Gotchas and should have been in the README (sorry)
The problem is that upstream and thus CentOS defaults to thinking your system clock is set to UTC (for some gosh-darn reason after years of not having this as a default.. upstream decided to go back to it..
# /etc/sysconfig/clock # The ZONE parameter is only evaluated by system-config-date. # The timezone of the system is defined by the contents of /etc/localtime. ZONE="America/Denver" UTC=true ARC=false
change UTC=true to UTC=false
The BIOS has the correct time and date on it. /etc/locatime was originally what /usr/share/zoneinfo/America/Denverwould've been. I removed it and symlinked it instead thinking it might change things - it didn't.
Right now, 'date' tells me: [1] 13:21:12 <root@bigbertha:~> date Sat Apr 14 13:21:13 MDT 2007 But it's actually 19:21... So, uh, what's going on? Why is the time so off? Under CentOS 4,the time was just fine. Something happened in 5.
-- H | It's not a bug - it's an undocumented feature. +-------------------------------------------------------------------- Ashley M. Kirchner mailto:ashley@pcraft.com . 303.442.6410 x130 IT Director / SysAdmin / Websmith . 800.441.3873 x130 Photo Craft Imaging . 3550 Arapahoe Ave. #6 http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Stephen John Smoogen wrote:
The problem is that upstream and thus CentOS defaults to thinking your system clock is set to UTC (for some gosh-darn reason after years of not having this as a default.. upstream decided to go back to it..
Nice! That is the Unix way of doing it. Since Unix always keep time in UTC/GMT, it makes sense to have the CMOS clock do the same.
//Morten
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sat, Apr 14, 2007 at 07:21:11PM -0600, Ashley M. Kirchner wrote:
I installed CentOS 5 on a server today (wiping clean the drive which had 4.4 on it). During installation I picked the correct timezone, location and all. Yet, upon booting the machine, it seems to think that it's 6 hours earlier than it really is.
The BIOS has the correct time and date on it.
/etc/locatime was originally what /usr/share/zoneinfo/America/Denver would've been. I removed it and symlinked it instead thinking it might change things - it didn't.
Right now, 'date' tells me:
[1] 13:21:12 <root@bigbertha:~> date Sat Apr 14 13:21:13 MDT 2007But it's actually 19:21...
So, uh, what's going on? Why is the time so off? Under CentOS 4, the time was just fine. Something happened in 5.
It seems like you selected "BIOS time is UTC", or something like it.
Change UTC to false on /etc/sysconfig/clock, set the clock manually (with "date"), then write to bios (hwclock --systohc).
[]s
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
-
Ashley M. Kirchner -
Morten Torstensen -
Rodrigo Barbosa -
Stephen John Smoogen