From owner-freebsd-questions@FreeBSD.ORG  Sun Jul  6 21:15:03 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id DBBCDBBC
 for <freebsd-questions@freebsd.org>; Sun,  6 Jul 2014 21:15:03 +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 97FC2262F
 for <freebsd-questions@freebsd.org>; Sun,  6 Jul 2014 21:15:03 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by mailout4.easymail.ca (Postfix) with ESMTP id 736A0E7B3
 for <freebsd-questions@freebsd.org>; Sun,  6 Jul 2014 17:14:56 -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 F1jeqitsdQUD for <freebsd-questions@freebsd.org>;
 Sun,  6 Jul 2014 17:14:54 -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 539DFE7B2
 for <freebsd-questions@freebsd.org>; Sun,  6 Jul 2014 17:14:54 -0400 (EDT)
Message-ID: <53B9BC4B.4030609@gooch.io>
Date: Sun, 06 Jul 2014 14:14:51 -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>
In-Reply-To: <20140706153206.GA46262@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: Sun, 06 Jul 2014 21:15:03 -0000

Hi Victor,

On 06/07/14 08:32 AM, Victor Sudakov wrote:
> Colleagues,
> 
> What's the command to update the CMOS clock to the time of the kernel
> clock? 
> 
> ntpd does a good job of keeping the accurate time in the kernel clock,
> but from my experience, this time is not propagated to the CMOS clock
> which lives its own life. As a result, there is a large time skew
> everytime the box is rebooted, which prevents from Kerberos login
> until the kernel clock is synchronized.
> 
> In other words, what's the FreeBSD equivalent of the Linux 
> "hwclock --systohc" command? 
> 
> And no, contrary to popular belief, the correction of the CMOS clock
> does not happen automatically in FreeBSD even if ntpd is running.
> 
> If there is a way to display the time of the CMOS (RTC) clock, I
> would be interested to know too.
> 
> TIA.
> 

To get around this I've started using ntpdate on boot. You can put the
following in your /etc/rc.conf:

---
ntpdate_enable="YES"
ntpdate_flags="<time server here>"
---