From owner-freebsd-questions@FreeBSD.ORG Sat Feb 12 11:07:53 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C3DF106564A for ; Sat, 12 Feb 2011 11:07:53 +0000 (UTC) (envelope-from cjr@cruwe.de) Received: from cruwe.de (t1850.greatnet.de [83.133.124.96]) by mx1.freebsd.org (Postfix) with ESMTP id DE3728FC08 for ; Sat, 12 Feb 2011 11:07:52 +0000 (UTC) Received: (qmail 30645 invoked from network); 12 Feb 2011 11:07:50 -0000 Received: from p57bdeeb5.dip.t-dialin.net (HELO dijkstra) (smtpallow@87.189.238.181) by t1850.greatnet.de with ESMTPA; 12 Feb 2011 11:07:50 -0000 Date: Sat, 12 Feb 2011 12:07:41 +0100 From: "Christopher J. Ruwe" To: freebsd-questions@freebsd.org Message-ID: <20110212120741.64de120f@dijkstra> In-Reply-To: <20110211220106.766288e5@gumby.homeunix.com> References: <20110211221648.03c65a04@dijkstra> <20110211220106.766288e5@gumby.homeunix.com> X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/A7BwYbwemAGFo71WW19E69o"; protocol="application/pgp-signature" Subject: Re: system clock running 2h early although ntpd enabled 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: Sat, 12 Feb 2011 11:07:53 -0000 --Sig_/A7BwYbwemAGFo71WW19E69o Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 11 Feb 2011 22:01:06 +0000 RW wrote: > On Fri, 11 Feb 2011 12:13:43 -0800 > David Brodbeck wrote: >=20 > > On Fri, Feb 11, 2011 at 1:16 PM, Christopher J. Ruwe > > wrote: > > > Since some weeks my local clock runs two hours early. > > > My /etc/localtime is a copy of /usr/share/zoneinfo/Europe/Berlin > > > and I have set both ntpd_enable=3D"YES" and > > > ntpd_sync_on_start=3D"YES". > >=20 > > ntpd has a sanity check -- if the clock is out by more than 1000 > > seconds it will give up. So you may have to manually set the clock > > to something close to correct before ntpd will handle it. Or pass > > ntpd the "-g" flag to disable the initial sanity check,=20 >=20 > That's what ntpd_sync_on_start=3D"YES" does. Which implies that you are booting. In my case, I normally suspend and resume, so that the ntpd_sync_on_start=3D"YES" does not really help. Thanks for the clarification anyway, I would not have known that part otherwise. Cheers, --=20 Christopher J. Ruwe TZ GMT + 1 --Sig_/A7BwYbwemAGFo71WW19E69o Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iQIcBAEBAgAGBQJNVmoDAAoJEJTIKW/o3iwUU14QAOE4Lk80AzgsaZjJhWt6nu5x Flf0VDaEFFd6SXTGQ4YODKoTSXVoFIZOEHvcKXMyiNw8SUUi7PAxstt03APJ1JYc hPeVdT6QSRV4900OjUZFrokDyNC69j+fKn3NfS0Ap+fKA/nZ49ijrridRe0V13s/ h1ridsSovZt86YGpAivNwjMPFvJu5ZDBF4JBr7CiTQ5RXPpo4gstdem6+vykH9Cf 827hhSfGylI1kKr35L41OzLkbjTX8MpuQLfIAtmgjH+WjSoax68C+RE98kTWuIhX Ngu3tJ/bq0TT17HFhLlPMP+vxmQu0jC/AIGgWIgXW7wkxWJikVterwjUG3+KsQHD Mn0wNcHPrqrJUL/bOBufkRbsaB5FaSa1IhsSgKDsdjZRfrKk48QEGBav/NHgZWjw iraQG8dK9Mz1FuB2wAzmeNwb4QvtE7vnvgl7h6bxLUgRhzCyZq57/z8LzY0QdMJB kMLUeNer3CopejNrLechFTHPijBrS3VS8EI9rBM0E/8edcN5fH/uc6O3nTHEv/PJ fn0ire6m6rlabjHlhVAyid1wv+zjmQx6fs54h71xsDbOPqKvNS0DJe4AZgkacN5b uTRLLJnxMDZ1wVSjpWTxtOuT3tFca0+oZuz0Rcruj8SIXd5ogvxbIrCOpbGO+NTO YC0IQG653yRNOEKZNZ5H =HXJk -----END PGP SIGNATURE----- --Sig_/A7BwYbwemAGFo71WW19E69o--