From owner-freebsd-questions@FreeBSD.ORG Mon Jul 7 13:40:42 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 651C0CA3 for ; Mon, 7 Jul 2014 13:40:42 +0000 (UTC) Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EF9D526A6 for ; Mon, 7 Jul 2014 13:40:41 +0000 (UTC) Received: by mail-wg0-f43.google.com with SMTP id b13so4354306wgh.26 for ; Mon, 07 Jul 2014 06:40:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=fmWaz8A/tPiJbzIrPAqn33s39rG7tORkIRrgoLVwOos=; b=nCH02360uO594PKuv7kqagZAkknvadRJklUh7X1HjVcpGqm52uCyJ2LKvPloIKRrvb OovD1IBooMi3VIMg9tFzP0yTS7DeZXwLfCTPx9m0unJCKgn8Iyq4XImwj1/+Zx/IsEyN hSTx7THqcFIwn62iAFqPhKGyNeeC16X8gb7YAC1j87XvG+l33uXvsmWFdHUtu5QxQkPr XFV81eL5S4/Vklv4DWsnxoybTvTwBDsd6ZATUZxWu+SQfMq1AjdMOcuNZkdlVmnW6OwN 4oWXP9/SdzLThcfF2yE2uNHe2i+KtulzyBYvDcnB3iPUSwbK6bdV73VzBWh42ynJzCCH LEhA== X-Received: by 10.194.158.226 with SMTP id wx2mr4063666wjb.107.1404740439898; Mon, 07 Jul 2014 06:40:39 -0700 (PDT) Received: from gumby.homeunix.com (4e5670bd.skybroadband.com. [78.86.112.189]) by mx.google.com with ESMTPSA id cd1sm89523649wjc.19.2014.07.07.06.40.38 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Mon, 07 Jul 2014 06:40:39 -0700 (PDT) Date: Mon, 7 Jul 2014 14:40:33 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: Updating and displaying CMOS clock Message-ID: <20140707144033.4ec77a56@gumby.homeunix.com> In-Reply-To: References: <20140706153206.GA46262@admin.sibptus.tomsk.ru> <20140707130816.32fd9af2@gumby.homeunix.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 13:40:42 -0000 On Mon, 7 Jul 2014 15:15:34 +0200 (CEST) Trond Endrest=F8l wrote: > On Mon, 7 Jul 2014 13:08+0100, RW wrote: >=20 > > On Sun, 6 Jul 2014 22:32:07 +0700 > > Victor Sudakov wrote: > >=20 > >=20 > > > And no, contrary to popular belief, the correction of the CMOS > > > clock does not happen automatically in FreeBSD even if ntpd is > > > running. > >=20 > > Are you sure about that? That used to be the case, but I thought it > > was fixed in 10-CURRENT. > >=20 > > I haven't set my hardware clock manually in more than a year, and > > it's out by less than a second. >=20 > Check out /etc/crontab and the execution of adjkerntz(8). >=20 I run my RTC on UTC so there's no need for adjkerntz ever to change it. Even if it did it would have been set over 3 months ago, and it's pretty unlikely that the RTC would still be accurate to 1 second. As I mentioned in my follow-up it's actually being set every 30 minutes by the kernel. I was pretty sure that someone had worked on a fix for this, but I wasn't 100% certain that it had been committed - until I saw the sysctl.