public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Kapshuk <alexander.kapshuk@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Chrony-2.2 failing
Date: Thu, 19 Nov 2015 19:06:57 +0200	[thread overview]
Message-ID: <CAJ1xhMVe=ChKy4E2Kt+hVW-YBXRUhUrWtceDyHzb0uaUpPw09g@mail.gmail.com> (raw)
In-Reply-To: <2068412.puBuVpJXRl@wstn>

[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]

On Thu, Nov 19, 2015 at 12:49 PM, Peter Humphrey <peter@prh.myzen.co.uk>
wrote:

> Hello list,
>
> Chrony has been upgraded from 2.1.1 to 2.2 this week. The new version seems
> to run just fine on this amd64 box, but on my x86 Atom box it fails to
> start
> thus:
>
> # /etc/init.d/chronyd start
>  * Starting chronyd ...
>  * start-stop-daemon: caught an interrupt
>  * start-stop-daemon: /usr/sbin/chronyd died
>  * Failed to start chronyd                                     [ !! ]
>  * ERROR: chronyd failed to start
>
> This is after adjusting the config files. Has anyone else stumbled into
> this?
>
> What's more, earlier versions had a decent man page and heavily commented
> chronyd.conf, but now the chrony.conf man page has been cut to a bare
> minimum and instead refers to a file chrony.txt "included in the
> distribution". I cannot find any such file after running ebuild $(equery w
> chrony) prepare.
>
> --
> Rgds
> Peter
>
>
>
'/usr/share/info/chrony.info.bz2' seems to offer more complete
documentation.

chrony2.2 seems to be running OK on my system:

uname -p
Intel(R) Core(TM)2 Duo CPU E4600 @ 2.40GHz

Here's the contents of my 'chrony.conf', if that is of any help.

grep '^[a-z]' /etc/chrony/chrony.conf
server 0.pool.ntp.org iburst
server 1.pool.ntp.org iburst
server 2.pool.ntp.org iburst
maxupdateskew 5
driftfile /var/lib/chrony/drift
keyfile /etc/chrony/chrony.keys
commandkey 1
generatecommandkey
makestep 1.0 3
logdir /var/log/chrony
log measurements statistics tracking
rtcsync

[-- Attachment #2: Type: text/html, Size: 2205 bytes --]

  reply	other threads:[~2015-11-19 17:07 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 [this message]
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
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='CAJ1xhMVe=ChKy4E2Kt+hVW-YBXRUhUrWtceDyHzb0uaUpPw09g@mail.gmail.com' \
    --to=alexander.kapshuk@gmail.com \
    --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