I was just looking at using the -q option before actually running the daemon.
It appears to be broken.
Setting the option sets
clock_control = 0;
In SYS_Intialise(), only the null driver is loaded. The actual system drivers
are not loaded.
When chronyd then detects it needs to step the clock, the null driver is
invoked and that returns a failed code.
Bryan Christianson
br...@whatroute.net
--
To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe"
in the subject.
For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the
subject.
Trouble? Email listmas...@chrony.tuxfamily.org.
