From owner-freebsd-questions@FreeBSD.ORG  Mon Jul  7 04:57:24 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 94F805B5
 for <freebsd-questions@freebsd.org>; Mon,  7 Jul 2014 04:57:24 +0000 (UTC)
Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5])
 by mx1.freebsd.org (Postfix) with ESMTP id F2E0A2874
 for <freebsd-questions@freebsd.org>; Mon,  7 Jul 2014 04:57:23 +0000 (UTC)
X-Virus-Scanned: by clamd daemon 0.98.1 for FreeBSD at relay2.tomsk.ru
Received: from admin.sibptus.tomsk.ru (account sudakov@sibptus.tomsk.ru
 [212.73.125.240] verified)
 by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16)
 with ESMTPSA id 35936427; Mon, 07 Jul 2014 11:57:22 +0700
Received: from admin.sibptus.tomsk.ru (sudakov@localhost [127.0.0.1])
 by admin.sibptus.tomsk.ru (8.14.7/8.14.7) with ESMTP id s674vK7m063947;
 Mon, 7 Jul 2014 11:57:21 +0700 (NOVT)
 (envelope-from vas@mpeks.tomsk.su)
Received: (from sudakov@localhost)
 by admin.sibptus.tomsk.ru (8.14.7/8.14.7/Submit) id s674vKue063946;
 Mon, 7 Jul 2014 11:57:20 +0700 (NOVT)
 (envelope-from vas@mpeks.tomsk.su)
X-Authentication-Warning: admin.sibptus.tomsk.ru: sudakov set sender to
 vas@mpeks.tomsk.su using -f
Date: Mon, 7 Jul 2014 11:57:20 +0700
From: Victor Sudakov <vas@mpeks.tomsk.su>
To: Olivier Nicole <olivier.nicole@cs.ait.ac.th>
Subject: Re: Updating and displaying CMOS clock
Message-ID: <20140707045720.GA63735@admin.sibptus.tomsk.ru>
References: <20140706153206.GA46262@admin.sibptus.tomsk.ru>
 <53B9BC4B.4030609@gooch.io>
 <20140707021022.GB58025@admin.sibptus.tomsk.ru>
 <53BA0493.1030205@gooch.io>
 <20140707034300.GA60208@admin.sibptus.tomsk.ru>
 <CA+g+BvggA+4+k=M-nmGZtKxsDTQNf3QFM4r9ZB05F4VAMgS7KQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+g+BvggA+4+k=M-nmGZtKxsDTQNf3QFM4r9ZB05F4VAMgS7KQ@mail.gmail.com>
Organization: AO "Svyaztransneft", SibPTUS
X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov
X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9  3532 0DA4 F259 9B5E C634
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
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 04:57:24 -0000

Olivier Nicole wrote:
> 
> >> The drift on clocks integrated into computers these days is pretty
> >> terrible AFAIK, which is why NTP is so widespread.
> > If the hardware clock is updated maybe daily, I don't expect any
> > significant drift.
> 
> If all you need is a daily update, why not a cron to restart ntp once
> a day? 

Because no matter how often you restart ntp, it does not update the
CMOS (hardware) clock.

My question was about updating the CMOS clock.


-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:sudakov@sibptus.tomsk.ru