From owner-freebsd-questions@FreeBSD.ORG Tue Oct 17 22:56:06 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9390016A40F for ; Tue, 17 Oct 2006 22:56:06 +0000 (UTC) (envelope-from pgiessel@mac.com) Received: from achilles.leela.ws (achilles.leela.ws [66.207.162.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F25643D68 for ; Tue, 17 Oct 2006 22:56:06 +0000 (GMT) (envelope-from pgiessel@mac.com) Received: from [192.168.0.193] ([158.145.111.132]) (authenticated bits=0) by achilles.leela.ws (8.13.6/8.13.6) with ESMTP id k9HMu0gb055819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 17 Oct 2006 14:56:01 -0800 (AKDT) (envelope-from pgiessel@mac.com) Message-ID: <45355F80.3@mac.com> Date: Tue, 17 Oct 2006 14:56:00 -0800 From: "Peter A. Giessel" User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909) MIME-Version: 1.0 To: Derek Ragona References: <20061018000853.O49453@192.168.11.51> <6.0.0.22.2.20061017173933.021d56c8@mail.computinginnovations.com> In-Reply-To: <6.0.0.22.2.20061017173933.021d56c8@mail.computinginnovations.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Zbigniew Szalbot , freebsd-questions@freebsd.org Subject: Re: ntpd not adjusting the clock? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2006 22:56:06 -0000 On 2006/10/17 14:40, Derek Ragona seems to have typed: > ntpd won't correct the clock if the difference is too large. So you need > to kill ntpd, run ntpdate to set the clock, then start ntpd up again. > > -Derek > > > At 05:13 PM 10/17/2006, Zbigniew Szalbot wrote: >> ntpd_flags="-g -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntp.drift" >From "man ntpd": -g Normally, ntpd exits if the offset exceeds the sanity limit, which is 1000 s by default. If the sanity limit is set to zero, no sanity checking is performed and any offset is acceptable. This option overrides the limit and allows the time to be set to any value without restriction; however, this can happen only once. After that, ntpd will exit if the limit is exceeded. This option can be used with the -q option. With the "-g" flag in there, it shouldn't matter if the difference is too large.