From owner-freebsd-questions Sun Dec 30 10:10: 4 2001 Delivered-To: freebsd-questions@freebsd.org Received: from clink.schulte.org (clink.schulte.org [209.134.156.193]) by hub.freebsd.org (Postfix) with ESMTP id 5927C37B416 for ; Sun, 30 Dec 2001 10:09:58 -0800 (PST) Received: from schulte-laptop.nospam.schulte.org (unknown [206.168.194.190]) by clink.schulte.org (Postfix) with ESMTP id 926342440D; Sun, 30 Dec 2001 12:09:55 -0600 (CST) Message-Id: <5.1.0.14.0.20011230115456.041ea2d8@pop3s.schulte.org> X-Sender: (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 30 Dec 2001 12:09:24 -0600 To: "Casey Scott" , From: Christopher Schulte Subject: Re: NTP In-Reply-To: <000001c19105$03ccc520$0301a8c0@Collosys> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Your system's kernel securelevel is set to 2 or higher, which limits time changes to one second. verify with this command # sysctl kern.securelevel Then see http://www.freebsd.org/cgi/man.cgi?query=securelevel&sektion=8 and http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#SECURELEVEL To learn more and how to fix it. You cannot lower the securelevel while a system is running; you'll need to modify your rc.conf and reboot. You can then run ntpdate to update the time. I'd cron an ntpdate job to run every so often, so you can then bring your securelevel back to the original value. Thus your clock will never be more than one second off and you will not run into this problem again. At 02:38 AM 12/30/2001 -0500, Casey Scott wrote: > >Hello, > > I am trying to set a server's clock using the command "ntpdate". >It appears that the clock is not accurate, but the process doesn't >adjust the time. Here is "ntpdate -v": > >ntpdate -d 128.10.252.7 >30 Dec 02:40:13 ntpdate[8222]: ntpdate 4.0.99b Thu Oct 25 13:03:00 EST >2001 (1) >transmit(128.10.252.7) >receive(128.10.252.7) >transmit(128.10.252.7) >receive(128.10.252.7) >transmit(128.10.252.7) >receive(128.10.252.7) >transmit(128.10.252.7) >receive(128.10.252.7) >transmit(128.10.252.7) >server 128.10.252.7, port 123 >stratum 1, precision -19, leap 00, trust 000 >refid [GPS], delay 0.07053, dispersion 0.00150 >transmitted 4, in filter 4 >reference time: bfd9427c.00000000 Sun, Dec 30 2001 2:36:28.000 >originate timestamp: bfd9427d.40342e04 Sun, Dec 30 2001 2:36:29.250 >transmit timestamp: bfd9435e.42cfe9b7 Sun, Dec 30 2001 2:40:14.260 >filter delay: 0.09224 0.07053 0.07095 0.07202 > 0.00000 0.00000 0.00000 0.00000 >filter offset: -225.025 -225.035 -225.034 -225.034 > 0.000000 0.000000 0.000000 0.000000 >delay 0.07053, dispersion 0.00150 >offset -225.035133 > >30 Dec 02:40:14 ntpdate[8222]: step time server 128.10.252.7 offset >-225.035133 sec > >=========== > >Syslog reports the following which may be involved: > >/kernel: Time adjustment clamped to -1 second > >========== > > Neither ntpdate or ntpd seem to adjust the clock, though both indicate >a substantial difference in times. Does anyone have any suggestions? > > >Thanks, >Casey Scott > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message