[ntp:hackers] NTP Release Candidate 4.2.8p1-RC1 Released

Gary E. Miller gem at rellim.com
Tue Jan 27 03:09:07 UTC 2015


Yo Hal!

On Mon, 26 Jan 2015 18:16:38 -0800
Hal Murray <hmurray at megapathdsl.net> wrote:

> My standard verbose setup in ntp.conf which has most of what I need
> for glitch chasing:
> 
[...]
> logconfig =syncall +clockall +peerall +sysall

I added this

> 
> That will put a lot of stuff into ntpd.log (more than I want in my
> syslog).
> 
[...]
> filegen clockstats type day link
> filegen loopstats  type day link
> filegen peerstats  type day link
> filegen protostats type day link
> filegen rawstats   type day link
> filegen refstats   type day link
> filegen sysstats   type day link

I added these, not sure how they might help?

This is the only extra thing I see now:

robin ntp # fgrep 127.127.46 /var/log/ntp/*
/var/log/ntp/clockstats:57049 10837.938 127.127.46.0 good=0   badtime=0   baddate=0   badreply=0   recv=0  
/var/log/ntp/clockstats:57049 10901.938 127.127.46.0 good=0   badtime=0   baddate=0   badreply=0   recv=0  
/var/log/ntp/clockstats:57049 10965.938 127.127.46.0 good=0   badtime=0   baddate=0   badreply=0   recv=0  
/var/log/ntp/clockstats:57049 11029.938 127.127.46.0 good=0   badtime=0   baddate=0   badreply=0   recv=0  
/var/log/ntp/clockstats:57049 11093.938 127.127.46.0 good=0   badtime=0   baddate=0   badreply=0   recv=0  



> If you add:
>   fudge  127.127.46.0 flag4 1

Done.  Beyond the already reported clk_fault I still see nothing that
might help.  The SHM's work, and are now generating more logging, but
nothing on the JSON.

Any idea why I get clk_fault?

robin ~ # ntpd -g -d -d |& fgrep JSON
event at 0 GPSD_JSON(0) 8011 81 mobilize assoc 9036
event at 4 GPSD_JSON(0) 802b 8b clock_event clk_fault


RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97701
	gem at rellim.com  Tel:+1(541)382-8588


More information about the hackers mailing list