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 93F181384B4 for ; Fri, 27 Nov 2015 09:33:55 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0929C21C0D2; Fri, 27 Nov 2015 09:33:47 +0000 (UTC) Received: from smarthost01a.mail.zen.net.uk (smarthost01a.mail.zen.net.uk [212.23.1.1]) by pigeon.gentoo.org (Postfix) with ESMTP id DADA121C0C4 for ; Fri, 27 Nov 2015 09:33:45 +0000 (UTC) Received: from [82.69.80.10] (helo=wstn.localnet) by smarthost01a.mail.zen.net.uk with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1a2FPU-000Blt-Vj for gentoo-user@lists.gentoo.org; Fri, 27 Nov 2015 09:33:45 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Chrony-2.2 failing Date: Fri, 27 Nov 2015 09:33:44 +0000 Message-ID: <2599062.3cz5ENopyl@wstn> User-Agent: KMail/4.14.8 (Linux/4.1.12-gentoo; KDE/4.14.8; x86_64; ; ) In-Reply-To: <2037315.vz9mHKf7DN@wstn> References: <2068412.puBuVpJXRl@wstn> <5655EA68.6080608@gmail.com> <2037315.vz9mHKf7DN@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-smarthost01a-IP: [82.69.80.10] X-Archives-Salt: 39aee6da-db2e-414c-a04a-3c0fa0443526 X-Archives-Hash: 2d661e7bf69062f02ef2265125b194eb On Thursday 26 November 2015 10:39:56 I wrote: > On Wednesday 25 November 2015 19:05:44 Alan McKinnon wrote: > > On 24/11/2015 17:24, Peter Humphrey wrote: > --->8 > > > > 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. > > --->8 > > > 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. > > I've been offered one suggestion which will need me to make a local > overlay with a small code change. I'll try that and see what happens. The problem turns out to have been caused by the init script specifying --background to start-stop-daemon, which conflicts with chronyd's own forking to the background - at least, it does on my Atom box so it could elsewhere too. Stand ready, bgo. -- Rgds Peter