public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Chrony-2.2 failing
Date: Thu, 26 Nov 2015 10:39:56 +0000	[thread overview]
Message-ID: <2037315.vz9mHKf7DN@wstn> (raw)
In-Reply-To: <5655EA68.6080608@gmail.com>

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



  reply	other threads:[~2015-11-26 10:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 10:49 [gentoo-user] Chrony-2.2 failing Peter Humphrey
2015-11-19 17:06 ` Alexander Kapshuk
2015-11-19 17:17 ` Alan McKinnon
2015-11-20 10:22   ` Peter Humphrey
2015-11-20 11:03     ` Mick
2015-11-20 17:02       ` Peter Humphrey
2015-11-20 17:07         ` Alan McKinnon
2015-11-20 17:30           ` Mick
2015-11-21  9:59             ` Peter Humphrey
2015-11-24 15:24               ` Peter Humphrey
2015-11-25 17:05                 ` Alan McKinnon
2015-11-26 10:39                   ` Peter Humphrey [this message]
2015-11-26 13:00                     ` Neil Bothwick
2015-11-26 14:00                       ` Peter Humphrey
2015-11-26 15:04                         ` Neil Bothwick
2015-11-26 15:12                           ` Alan McKinnon
2015-11-27  9:33                     ` Peter Humphrey
2015-11-20 19:39           ` brettrsears
2015-11-19 21:15 ` Marc Joliet
2015-11-20  9:24   ` Peter Humphrey
2015-12-07 18:41     ` Mick
2015-11-20 17:02 ` Dale
2015-11-20 17:06   ` Peter Humphrey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2037315.vz9mHKf7DN@wstn \
    --to=peter@prh.myzen.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox