RE: Bind-chroot and ntp time

From: Cowles, Steve (steve_at_stevecowles.com)
Date: 07/01/04

  • Next message: Ow Mun Heng: "Re: FC2 freeze on splash screen [PARTIALLY SOLVED]" 
    To: "'For users of Fedora Core releases'" <fedora-list@redhat.com>
Date: Thu, 1 Jul 2004 14:21:02 -0500

    VCI Gold Support wrote:
    > 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
    >

    If your systems clock is set UTC (like mine), then you will need to copy
    /etc/localtime to bind's chroot'd etc directory to fix the time offset
    problem you describe. i.e /var/named/chroot/etc

    FWIW: I've had to do this since RH9.

    Steve Cowles 

    -- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Ow Mun Heng: "Re: FC2 freeze on splash screen [PARTIALLY SOLVED]"