From owner-freebsd-questions@FreeBSD.ORG Mon Jul 7 12:53:37 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 BB052B77 for ; Mon, 7 Jul 2014 12:53:37 +0000 (UTC) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (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 534AD2202 for ; Mon, 7 Jul 2014 12:53:37 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id bs8so6655501wib.3 for ; Mon, 07 Jul 2014 05:53:34 -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=lNuzGW3Hs/BhtR3hvR8qi3Ck2RY1etchTPBDHp4V7Lo=; b=wlJnuCqnr8N7FV17dsjgTW+oGvdhT8KzrkZWtYe+XKDAw5Y7Mf6OhI1+96xxwY/+O4 5WFgZ10U/Q8bwBRE9R4tupjdppJmvZ41xdNqZtc9dlG7cjEQQCwpIX1nUO0dOQfviIHh J1inEi9zxpHU4kgCuqHB9Ysyi5xwWkL+2+1YgsTF2PTXXkWxGgwRXLoQKC3YlNayNfAS TvO/9u4wxD0LBksi33iZXbFupWTSP9yLMPx8WDZdWbYm9A8kY614+Sadk7/xok7RkQX/ 3YWhvZfoXAFAzXhIDnsrF+QEaTWyUkLFWUoQoM08Jy3v3EgSQkWew51uFDfXHmGj4tbx 6MKA== X-Received: by 10.194.92.177 with SMTP id cn17mr32871856wjb.71.1404737614000; Mon, 07 Jul 2014 05:53:34 -0700 (PDT) Received: from gumby.homeunix.com (4e5670bd.skybroadband.com. [78.86.112.189]) by mx.google.com with ESMTPSA id ec8sm96009269wic.10.2014.07.07.05.53.33 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Mon, 07 Jul 2014 05:53:33 -0700 (PDT) Date: Mon, 7 Jul 2014 13:53:30 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: Updating and displaying CMOS clock Message-ID: <20140707135330.0cf030c7@gumby.homeunix.com> In-Reply-To: <20140707130816.32fd9af2@gumby.homeunix.com> 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=US-ASCII Content-Transfer-Encoding: 7bit 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 12:53:37 -0000 On Mon, 7 Jul 2014 13:08:16 +0100 RW wrote: > On Sun, 6 Jul 2014 22:32:07 +0700 > Victor Sudakov wrote: > > > > And no, contrary to popular belief, the correction of the CMOS clock > > does not happen automatically in FreeBSD even if ntpd is running. > > Are you sure about that? That used to be the case, but I thought it > was fixed in 10-CURRENT. I missed this: On Mon, 7 Jul 2014 17:39:55 +0700 Victor Sudakov wrote: > I have been told about the machdep.rtc_save_period sysctl, but it > seems undocumented. It looks like it has been fixed. I never followed the PR, but the solution discussed on the mailing list was to update the hardware clock from the system clock every 30 minutes $ sysctl -d machdep.rtc_save_period machdep.rtc_save_period: Save system time to RTC with this period (in seconds) $ sysctl machdep.rtc_save_period machdep.rtc_save_period: 1800