Bind-chroot and ntp time

[Alexander Dalloz]

Am Do, den 01.07.2004 schrieb VCI Gold Support um 17:47:

> On Fedora Core 2 , using bind-chroot we are seeing odd timestamps in the 
> messages log. The named seems to change the time from the system time 
> when it logs. Any ideas?
> 
> Jul  1 10:38:01 server snmpd[3731]: No swap line in /proc/stat
> Jul  1 15:38:20 server named[13824]: shutting down
> Jul  1 15:38:20 server named[13824]: no longer listening on 127.0.0.1#53
> Jul  1 15:38:20 server named[13824]: no longer listening on publicip#53
> Jul  1 15:38:20 server named[13824]: no longer listening on privateip#53
> Jul  1 15:38:20 server named[13824]: exiting
> Jul  1 10:38:20 server named: named shutdown succeeded

> Chris Moss

$ ls -al /var/named/chroot/etc/localtime
-rw-r--r--  1 root root 837 11. Dez 2003 
/var/named/chroot/etc/localtime

The localtime file in the chroot dir is the same as the one in /etc/.
IIRC someone on this list once reported that copying the localtime from
/etc/ into the bind chroot dir fixed his problems with odd bind logging
dates. I personally don't see such effects (still running FC1 on the
bind server).

Alexander


-- 
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 2 (Tettnang) on Athlon CPU kernel 2.6.6-1.435.2.1 
Serendipity 17:58:04 up 3:54, 8 users, 0.45, 0.56, 0.75 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20040701/288d26bb/attachment-0001.sig>