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 C225C1384B4 for ; Wed, 25 Nov 2015 17:07:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D755B21C092; Wed, 25 Nov 2015 17:06:53 +0000 (UTC) Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com [74.125.82.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 9C4B621C07F for ; Wed, 25 Nov 2015 17:06:52 +0000 (UTC) Received: by wmec201 with SMTP id c201so265991835wme.0 for ; Wed, 25 Nov 2015 09:06:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=zFznbuzLHlHPJkxDOm7UBW6YKegbRELR2HsmENCOMpk=; b=YetD8K6VMPmj2edMTHZe7zsQBuW7Ji6wremY2T58VkfAm81FOKmmTLKUCaiE8IaWwo dbSMsZdKh+K38yvDUMLMycpZTAiFtpLBhhKeqnrfzrmZ75GaTpDt7yBDqk0cqn2dRr26 2N4vgn22bql27UDxbmWZfhacX4KmMKAOV477rYf+dutxrQtbUdV68NaNuDRE2QXX1oGN yY6vwP9iWRoc/4v4K6gn1QGhvGkgt5ZFjCYgc1nIPZ6BFSHNVz26z52SeF6hKOvGbp9i DuVgjTCZLcGud0E1s9UqGLEzt0l64HvPyJCfVgO6tABiwvPNGdqHb0Y0PTpGCJl4XcR3 xKcg== X-Received: by 10.28.88.5 with SMTP id m5mr6149231wmb.54.1448471211544; Wed, 25 Nov 2015 09:06:51 -0800 (PST) Received: from [172.20.0.40] ([165.255.112.248]) by smtp.googlemail.com with ESMTPSA id u17sm4431980wmd.8.2015.11.25.09.06.50 for (version=TLSv1/SSLv3 cipher=OTHER); Wed, 25 Nov 2015 09:06:50 -0800 (PST) Subject: Re: [gentoo-user] Chrony-2.2 failing To: gentoo-user@lists.gentoo.org References: <2068412.puBuVpJXRl@wstn> <201511201730.58095.michaelkintzios@gmail.com> <2019751.jAPIc1Hiu1@wstn> <2404811.xJJSWLPkl9@wstn> From: Alan McKinnon Message-ID: <5655EA68.6080608@gmail.com> Date: Wed, 25 Nov 2015 19:05:44 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 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 In-Reply-To: <2404811.xJJSWLPkl9@wstn> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 964da080-a4b2-4ec6-8581-c8ec7da3ff45 X-Archives-Hash: ed091ad53b20c906c9f5a7b2cfe3932d On 24/11/2015 17:24, Peter Humphrey wrote: > 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. > Ugh, don't you just hate issues like that? The problem with "solutions" like start-stop-daemon is they have to deal with whatever the daemon feels like returning (an infinite number of permutations), so support for daemon is never complete. Regardless of what one thinks of systemd, this is one of the things it set out to deal with. There's only one way to start something, and it behaves one way, making behaviour considerably more predictable. [ A bit of a rant I know, but I'm still smarting from years of rancid and Cisco logins - basically the same kind of problem you are having on a much larger scale...] -- Alan McKinnon alan.mckinnon@gmail.com