From owner-freebsd-questions Thu Aug 20 10:28:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16308 for freebsd-questions-outgoing; Thu, 20 Aug 1998 10:28:09 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from greeves.mfn.org (greeves.mfn.org [204.238.179.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16050 for ; Thu, 20 Aug 1998 10:27:48 -0700 (PDT) (envelope-from sysadmin@mfn.org) Received: from noc.mfn.org (noc.mfn.org [204.238.179.35]) by greeves.mfn.org (8.8.7/8.8.7) with SMTP id MAA11602 for ; Thu, 20 Aug 1998 12:26:49 -0500 (CDT) (envelope-from sysadmin@mfn.org) Received: by noc.mfn.org with Microsoft Mail id <01BDCC34.A1E8DBC0@noc.mfn.org>; Thu, 20 Aug 1998 12:18:26 -0500 Message-ID: <01BDCC34.A1E8DBC0@noc.mfn.org> From: "sysadmin@mfn.org" To: "'freebsd-questions@freebsd.org'" Subject: Anything Special about 1930? Date: Thu, 20 Aug 1998 12:18:10 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 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: jb214@ns2$ ps -wax 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 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? TIA, J.A. Terranson sysadmin@mfn.org "If government wants us to behave, then it should set a better example." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message