From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 8E13F1384B4 for ; Tue, 24 Nov 2015 15:24:52 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7F776E0866; Tue, 24 Nov 2015 15:24:39 +0000 (UTC) Received: from smarthost03b.mail.zen.net.uk (smarthost03b.mail.zen.net.uk [212.23.1.21]) by pigeon.gentoo.org (Postfix) with ESMTP id 65725E0855 for ; Tue, 24 Nov 2015 15:24:38 +0000 (UTC) Received: from [82.69.80.10] (helo=wstn.localnet) by smarthost03b.mail.zen.net.uk with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1a1FSO-0007Au-DT for gentoo-user@lists.gentoo.org; Tue, 24 Nov 2015 15:24:36 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Chrony-2.2 failing Date: Tue, 24 Nov 2015 15:24:35 +0000 Message-ID: <2404811.xJJSWLPkl9@wstn> User-Agent: KMail/4.14.8 (Linux/4.1.12-gentoo; KDE/4.14.8; x86_64; ; ) In-Reply-To: <2019751.jAPIc1Hiu1@wstn> References: <2068412.puBuVpJXRl@wstn> <201511201730.58095.michaelkintzios@gmail.com> <2019751.jAPIc1Hiu1@wstn> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-smarthost03b-IP: [82.69.80.10] X-Archives-Salt: 92000f6a-dd7e-4c46-8de9-fa915eaad99b X-Archives-Hash: 9e7360e445793b04315d3724524c07fc On Saturday 21 November 2015 09:59:18 I wrote: > I think I'll follow Alan's suggestion and head upstream. After some discussion with Miroslav Lichvar I've found a chrony.conf that works for me on my 32-bit 2-core Atom. This is it: pool pool.ntp.org iburst server ntp0.zen.co.uk iburst server ntp1.zen.co.uk iburst driftfile /var/lib/chrony/drift makestep 1.0 3 allow 192.168.1/24 mailonchange prh@serv.prhnet 0.5 rtcfile /var/lib/chrony/rtc rtconutc The installation-default file causes the start-stop-daemon to catch an unexpected interrupt and report an error, even though the chronyd process continues to run. Any time I run 'strace -ff -o/tmp/chronyd.strace /etc/init.d/chronyd start' the init process runs normally and I'm left with scores of trace files, none of which help because the stray interrupt wasn't detected. So I'm left with a setup that works for me but leaves what looks (to me) like a timing problem unsolved. I'll report back if I hear any more. -- Rgds Peter