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 173F31384B4 for ; Thu, 26 Nov 2015 10:40:09 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0B25221C112; Thu, 26 Nov 2015 10:39:59 +0000 (UTC) Received: from smarthost01d.mail.zen.net.uk (smarthost01d.mail.zen.net.uk [212.23.1.7]) by pigeon.gentoo.org (Postfix) with ESMTP id 90D1421C10D for ; Thu, 26 Nov 2015 10:39:57 +0000 (UTC) Received: from [82.69.80.10] (helo=wstn.localnet) by smarthost01d.mail.zen.net.uk with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1a1ty0-0007zG-PJ for gentoo-user@lists.gentoo.org; Thu, 26 Nov 2015 10:39:56 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Chrony-2.2 failing Date: Thu, 26 Nov 2015 10:39:56 +0000 Message-ID: <2037315.vz9mHKf7DN@wstn> User-Agent: KMail/4.14.8 (Linux/4.1.12-gentoo; KDE/4.14.8; x86_64; ; ) In-Reply-To: <5655EA68.6080608@gmail.com> References: <2068412.puBuVpJXRl@wstn> <2404811.xJJSWLPkl9@wstn> <5655EA68.6080608@gmail.com> 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-smarthost01d-IP: [82.69.80.10] X-Archives-Salt: 59c462c3-dca1-4238-b5fd-421fcfc04f2f X-Archives-Hash: f93a2cf9a599f78bdf9bf666fc6af130 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. > 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. So it does occasionally have one benefit then. > [ 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...] I'll be content with my tiny scale, thanks very much :) -- Rgds Peter