comp.protocols.time.ntp
Affichage de l'article :
ntpd oddness

Date : Le 01 avril 2008
From : John Oliver
Sujet : ntpd oddness

I'm having a small issue with ntp-4.2.0.a.20040617-6.el4 running under
Red Hat Enterprise Linux 4 update 5.

In the Kickstart script to configure the server, I specify:

timezone --utc GMT/London

After the installation is done:

[joliver@0123456789-VCS ~]$ date
Tue Apr 1 17:03:23 EDT 2008

/etc/localtime is a real file:

[joliver@0123456789-VCS ~]$ ls -l /etc/localtime
-rw-r--r-- 1 root root 1267 Jan 31 2007 /etc/localtime

If I remove that file and replace it with a symlink:

[joliver@0123456789-VCS ~]$ ls -l /etc/localtime
lrwxrwxrwx 1 root root 23 Apr 1 21:04 /etc/localtime ->
/usr/share/zoneinfo/GMT

The system clock displays correctly:

[joliver@0123456789-VCS ~]$ date
Tue Apr 1 21:05:09 GMT 2008

But, now, the hwclock is always 12 hours off:

[joliver@0123456789-VCS ~]$ /sbin/hwclock
Tue 01 Apr 2008 09:05:39 PM GMT -0.323329 seconds
[joliver@0123456789-VCS ~]$ sudo /sbin/hwclock --systohc
[joliver@0123456789-VCS ~]$ /sbin/hwclock
Tue 01 Apr 2008 09:05:52 PM GMT -0.776568 seconds


1) Why is /etc/localtime a file by default instead of a symlink? Is
this just some silly Red Hat-ism that has to be avoided?

2) Why is my hardware clock 12 hours off from the system clock?

--
* John Oliver http://www.john-oliver.net/ *

--
Posted via a free Usenet account from http://www.teranews.com

Posez vos questions, réponses et remarques sur les forums de FrameIP