From owner-freebsd-questions@FreeBSD.ORG Sun Jul 6 21:03:59 2014 Return-Path: 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 A8D1F809 for ; Sun, 6 Jul 2014 21:03:59 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 54E85255B for ; Sun, 6 Jul 2014 21:03:59 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id s66L3vs0036522 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 6 Jul 2014 15:03:57 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id s66L3t2X036519; Sun, 6 Jul 2014 15:03:57 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 6 Jul 2014 15:03:55 -0600 (MDT) From: Warren Block To: Victor Sudakov Subject: Re: Updating and displaying CMOS clock In-Reply-To: <20140706153206.GA46262@admin.sibptus.tomsk.ru> Message-ID: References: <20140706153206.GA46262@admin.sibptus.tomsk.ru> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 06 Jul 2014 15:03:58 -0600 (MDT) Cc: freebsd-questions@freebsd.org 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: Sun, 06 Jul 2014 21:03:59 -0000 On Sun, 6 Jul 2014, Victor Sudakov wrote: > In other words, what's the FreeBSD equivalent of the Linux > "hwclock --systohc" command? Offhand, I don't know. But date(1) sets both kernel and hardware clocks, so a hacky way to do that is date -v +0S > And no, contrary to popular belief, the correction of the CMOS clock > does not happen automatically in FreeBSD even if ntpd is running. I'm a little surprised about that, too, although the relatively large adjustment in time after a reboot is an indicator. Now that you mention it, anyway.