From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-157427-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	by finch.gentoo.org (Postfix) with ESMTP id 4EC3E13877A
	for <garchives@archives.gentoo.org>; Sun, 27 Jul 2014 12:19:47 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 43277E0BD8;
	Sun, 27 Jul 2014 12:19:39 +0000 (UTC)
Received: from mail-we0-f177.google.com (mail-we0-f177.google.com [74.125.82.177])
	(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 0BF9FE0AF4
	for <gentoo-user@lists.gentoo.org>; Sun, 27 Jul 2014 12:19:37 +0000 (UTC)
Received: by mail-we0-f177.google.com with SMTP id w62so5999614wes.8
        for <gentoo-user@lists.gentoo.org>; Sun, 27 Jul 2014 05:19:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        bh=DfD+2+6Slshhr3JbLC9SFVN87FuARVaN40Kp8dUwqCg=;
        b=wODBV/2pxIqsPkL2a5XCUxDZATVZ2mwfy1szo8tP5GiO7AvTq/4fEAGsnp+dunPUEX
         Rz8P5SyWvuzmUrJN28buYY9YA13Q4C193H/ZYUTvt96IcObjtU80+X7lMl1aKuoOx0jV
         A/PSSkjpTmfTte7mT5Hy4HZ1UiDh1bJ+TMImIJfphod4lqyoL2iwKTbylTuf1Lt/Nsr+
         pZyfy7i/QQEILOXsEs2hSvCOWyHT5BMW7Bmwkf3Xyhb4a348tK5Hgb2/GeG1tNAS3WLE
         dCCyI0KSqsOgpKZ8cnL2wvcLHBTRsBoB6+EEHwYuFmFDxfKbfgJI5E7dVI5itMmrTAc7
         Ncfw==
X-Received: by 10.180.91.111 with SMTP id cd15mr7655988wib.69.1406463576702;
        Sun, 27 Jul 2014 05:19:36 -0700 (PDT)
Received: from [192.168.1.2] (213-154-212-42.static.vega-ua.net. [213.154.212.42])
        by mx.google.com with ESMTPSA id go4sm41085147wjc.39.2014.07.27.05.19.35
        for <gentoo-user@lists.gentoo.org>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Sun, 27 Jul 2014 05:19:36 -0700 (PDT)
Message-ID: <53D4EE57.2040700@gmail.com>
Date: Sun, 27 Jul 2014 15:19:35 +0300
From: Alexander Kapshuk <alexander.kapshuk@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: re: which NTPd package to use?
References: <53D39983.8050706@gmail.com> <pan.2014.07.26.12.31.55@googlemail.com> <53D3EFEC.1060100@gmail.com> <53D40ECD.2030602@gmail.com>
In-Reply-To: <53D40ECD.2030602@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-Archives-Salt: b44bd6cf-8522-409e-82c6-1b26cda99973
X-Archives-Hash: 3533c9a89c27de768c9db060936ffdb3

On 07/26/2014 11:25 PM, Dale wrote:
> Alexander Kapshuk wrote:
>> On 07/26/2014 03:31 PM, Holger Hoffstätte wrote:
>>> On Sat, 26 Jul 2014 15:05:23 +0300, Alexander Kapshuk wrote:
>>>
>>>> Which NTPd package would the list recommend using, ntp, openntpd, or
>>>> some other package?
>>> chrony - no competition, even for servers. ntpd is way overrated,
>>> unnecessarily hard to setup correctly, fragile and contrary to
>>> popular belief not even that accurate, unless you use external
>>> HW clocks. Chrony is maintained by Red Hat in cooperation with the
>>> timekeeping code in the kernel.
>>>
>>>> openntpd seems to be easier to set up according to wiki.gentoo.org.
>>> Many many years ago I helped port openntpd to Linux. It was OK-ish at
>>> the time and easier/less hassle than ntpd, but the portable version for
>>> Linux stopped working reliably many years ago due to kernel changes.
>>> IMHO it really should no longer be in the tree since it gives a false
>>> sense of accuracy.
>>>
>>> just my 0.01€..
>>>
>>> -h
>>>
>>>
>> Is this gentoo wiki article still relevant when it comes to configuring
>> chrony on gentoo?
>> http://www.gentoo-wiki.info/Chrony
>>
>> Or should I stick to the instructions given here:
>> /usr/share/doc/chrony-1.29.1/chrony.txt.bz2
>>
>> Thanks.
>>
>>
>>
>
> This is my chrony.conf without all the commented out parts. 
>
> server  64.6.144.6
> server  67.159.5.90
> server  67.59.168.233
> server  204.62.14.98
>
> server  69.50.219.51
> server  209.114.111.1
>
> driftfile /etc/chrony.drift
>
> keyfile /etc/chrony/chrony.keys
>
> commandkey 1
>
> logdir /var/log/chrony
> log measurements statistics tracking rtc
>
>
> The last two lines are optional.  Use those if you like to be nosy and
> watch it do its thing.  I still have ntpdate installed and use it to
> check and see how close it is on occasion.  This is what I get from the
> test:
>
> root@fireball / # ntpdate -b -u -q pool.ntp.org
> server 198.144.194.12, stratum 2, offset -0.003320, delay 0.10658
> server 173.44.32.10, stratum 2, offset -0.003313, delay 0.07515
> server 70.60.65.40, stratum 2, offset -0.003059, delay 0.09262
> server 38.229.71.1, stratum 2, offset -0.001002, delay 0.09563
> 26 Jul 15:16:00 ntpdate[10232]: step time server 173.44.32.10 offset
> -0.003313 sec
> root@fireball / # 
>
> I did a fair sized upgrade the other day and went to the boot runlevel
> afterwards to restart the services that were updated.  I'm pretty sure
> it has been doing its thing since then without me doing anything to it. 
> I think you can use mirrorselect to find the best mirrors for your
> area.  I can't recall the command but I bet a search of the Gentoo
> forums would find it fairly quick. 
>
> Looking at the howto, the only thing I do different is put it in the
> default runlevel.  Unless I am in the default runlevel, there is no
> internet access available anyway.  No internet access, no way to set the
> clock anyway.  ;-)
>
> Hope that helps.
>
> Dale
>
> :-)  :-) 
>
Terrific. Thanks.