From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Chrony-2.2 failing
Date: Sat, 21 Nov 2015 09:59:18 +0000 [thread overview]
Message-ID: <2019751.jAPIc1Hiu1@wstn> (raw)
In-Reply-To: <201511201730.58095.michaelkintzios@gmail.com>
On Friday 20 November 2015 17:30:56 Mick wrote:
> On Friday 20 Nov 2015 17:07:47 Alan McKinnon wrote:
> > On 20/11/2015 19:02, Peter Humphrey wrote:
> > > On Friday 20 November 2015 11:03:55 Mick wrote:
> > >> On Friday 20 Nov 2015 10:22:00 Peter Humphrey wrote:
> > >>> As I said, chronyd works on this four-core i5 box, just not on the
> > >>> two-core Atom.
> > >>
> > >> Have a look in the kernel of the Atom box and compare the RTC
> > >> settings
> > >> between the two boxen.
> > >
> > > Well, that was instructive - thanks Mick. I found a couple of settings
> > > I'm sure I'd never have set knowingly, one of them a debug. After
> > > removing them I still get the caught-an-interrupt and failed-to-start
> > > errors, but now I find that chrony is apparently running well despite
> > > the errors. At any rate, it logs the selection of a source five
> > > seconds
> > > after it's started and the
> > >
> > > process is still running:
> > > 2051 ? S 0:00 /usr/sbin/chronyd -f /etc/chrony/chrony.conf -s
> > > -r
> > >
> > > I've had another check through the kernel config, comparing it with
> > > the
> > > i5 config, and I've removed several more things that I think shouldn't
> > > be there, but it's made no further difference.
> >
> > Well that's interesting. I suggest at this point you ask at chrony's
> > support list - they'd know better than others what RTC settings their
> > software needs.
>
> I don't know what your settings are, but using the suggested by the ebuild
> new config file (which is *very* much a stipped down sample of the
> previous version) mine is not run with -s or -r.
>
> I tried running chrony with all my old configuration settings and it
> barfed on number of my entries. So I suggest that you first run it with
> only the settings provided in
> /usr/share/doc/chrony-2.2/chrony.conf.example1.bz2 and then modify one
> setting at a time.
My first attempt to get chronyd running was with only the newly installed,
stripped-down config, which I think is the same as that example. That's
where all the trouble started. And all along, I've been comparing the
configs on the two boxes and sometimes tweaking things.
I think I'll follow Alan's suggestion and head upstream.
--
Rgds
Peter
next prev parent reply other threads:[~2015-11-21 9:59 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 [this message]
2015-11-24 15:24 ` Peter Humphrey
2015-11-25 17:05 ` Alan McKinnon
2015-11-26 10:39 ` Peter Humphrey
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=2019751.jAPIc1Hiu1@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