On 19/11/2015 12:49, Peter Humphrey 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. >
Doe sit fail consistently? IOW, now that everything else has settled down, does "/etc/init.d/chrony start" still fail? What about logs? If none, you can inspect the start-stop-daemon line in the init file, get the command line it launches chrony with, and see what that prints to the console. -- Alan McKinnon alan.mckin...@gmail.com
