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