From owner-freebsd-questions Sat Aug 22 21:34:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25249 for freebsd-questions-outgoing; Sat, 22 Aug 1998 21:34:25 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25232 for ; Sat, 22 Aug 1998 21:34:19 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id VAA01586; Sat, 22 Aug 1998 21:33:30 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Sat, 22 Aug 1998 21:33:29 -0700 (PDT) From: Doug White To: "sysadmin@mfn.org" cc: "'freebsd-questions@freebsd.org'" Subject: Re: Anything Special about 1930? In-Reply-To: <01BDCC34.A1E8DBC0@noc.mfn.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 20 Aug 1998, sysadmin@mfn.org wrote: > Greetings. > > Once again, I present with a tale of the weird: My secondary > nameserver has always had the wrong time, but since it does > nothing but DNS, I've never bothered to correct it: until yesterday. > > Like all of our machines, it runs ntpdate -sb on bootup and > at midnight every day. Nevertheless, heres ns2's "date": > > jb214@ns2$ date > > Sat Aug 2 08:57:13 CDT 1930 > > And here are the relevent log entries: > > Aug 1 19:06:58 ns2 ntpdate[200]: step time server 192.52.106.6 offset 0.001704 > Aug 1 19:09:25 ns2 named[85]: secondary zone "mfn.org" time warp > Aug 1 19:47:57 ns2 named[85]: secondary zone "mfn.org" time warp > Aug 1 20:04:27 ns2 named[85]: secondary zone "mfn.org" time warp > Aug 1 20:37:54 ns2 named[85]: secondary zone "mfn.org" time warp I think named reports this when the zone file's date seems to go backwards in time. > Since NS2 is "headless" and I'll leave this as is if I can't resolve > it *easily*, but I'm puzzled. Why won't ntpdate correct the date? Also, > the time is off, even though I have the time zone set and the daemon > running: You might check the system log. The system battery may be dead. > PID TT STAT TIME COMMAND > 0 ?? DLs 0:00.57 (swapper) > 1 ?? IWs 0:00.22 /sbin/init -- > 2 ?? DL 0:00.79 (pagedaemon) > 3 ?? DL 0:01.87 (vmdaemon) > 4 ?? DL 0:14.74 (update) > 23 ?? IWs 0:00.06 adjkerntz -i > 80 ?? Ss 0:04.79 ^^^^^^^^^^^ anonymous process?? > Go figure? While I'm at it, what does the "time warp" message > actually *mean*? I can *see* that the time is wrong, but how > is it that named knows something is wrong? And precisely > what is it that named is trying to tell me? Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message