From owner-freebsd-questions@FreeBSD.ORG  Mon Jul  7 02:23:23 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
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 12888CDC
 for <freebsd-questions@freebsd.org>; Mon,  7 Jul 2014 02:23:23 +0000 (UTC)
Received: from mailout4.easymail.ca (mailout.easymail.ca [64.68.200.169])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id C3A902CEF
 for <freebsd-questions@freebsd.org>; Mon,  7 Jul 2014 02:23:21 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by mailout4.easymail.ca (Postfix) with ESMTP id 806C2E7A2
 for <freebsd-questions@freebsd.org>; Sun,  6 Jul 2014 22:23:20 -0400 (EDT)
X-Virus-Scanned: Debian amavisd-new at mailout4.easymail.ca
X-Spam-Flag: NO
X-Spam-Score: -4.399
X-Spam-Level: 
X-Spam-Status: No, score=-4.399 required=5 tests=[ALL_TRUSTED=-1.8,
 BAYES_00=-2.599]
Received: from mailout4.easymail.ca ([127.0.0.1])
 by localhost (easymail-mailout2.easydns.vpn [127.0.0.1]) (amavisd-new,
 port 10024)
 with ESMTP id P9rah6e1Hf5B for <freebsd-questions@freebsd.org>;
 Sun,  6 Jul 2014 22:23:20 -0400 (EDT)
Received: from localhost.localdomain (76-10-185-178.dsl.teksavvy.com
 [76.10.185.178])
 (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mailout4.easymail.ca (Postfix) with ESMTPSA id EE9A2E768
 for <freebsd-questions@freebsd.org>; Sun,  6 Jul 2014 22:23:19 -0400 (EDT)
Message-ID: <53BA0493.1030205@gooch.io>
Date: Sun, 06 Jul 2014 19:23:15 -0700
From: Jesse Gooch <lists@gooch.io>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: freebsd-questions@freebsd.org
Subject: Re: Updating and displaying CMOS clock
References: <20140706153206.GA46262@admin.sibptus.tomsk.ru>
 <53B9BC4B.4030609@gooch.io> <20140707021022.GB58025@admin.sibptus.tomsk.ru>
In-Reply-To: <20140707021022.GB58025@admin.sibptus.tomsk.ru>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jul 2014 02:23:23 -0000

Hi Victor,

On 06/07/14 07:10 PM, Victor Sudakov wrote:
> Jesse Gooch wrote:
>>>
>>> What's the command to update the CMOS clock to the time of the kernel
>>> clock? 
> 
> [dd]
> 
>>>
>>
>> To get around this I've started using ntpdate on boot. You can put the
>> following in your /etc/rc.conf:
>>
>> ntpdate_enable="YES"
> 
> ntpd_sync_on_start="YES" does the same, but it is not an answer to the
> question, it is a workaround. 
> 

Sure, it's a workaround. Why is it so important to set the CMOS clock if
you can just query the current time from a more accurate source on boot?
The drift on clocks integrated into computers these days is pretty
terrible AFAIK, which is why NTP is so widespread.