[LinuxPPS] ntpd
Folkert van Heusden
folkert at vanheusden.com
Thu Aug 3 17:19:23 CEST 2006
> > So if I have this in my dmesg:
> > [43015424.110000] drivers/pps/pps.c: New message from PID 23071 (flags 0)
> > [43015424.110000] drivers/pps/pps.c: PPS_FETCH: source 1
> > [43015425.110000] drivers/pps/pps.c: New message from PID 23071 (flags 0)
> > [43015425.110000] drivers/pps/pps.c: PPS_FETCH: source 1
> > [43015426.110000] drivers/pps/pps.c: New message from PID 23071 (flags 0)
> > [43015426.110000] drivers/pps/pps.c: PPS_FETCH: source 1
> > [43015427.110000] drivers/pps/pps.c: New message from PID 23071 (flags 0)
> > [43015427.110000] drivers/pps/pps.c: PPS_FETCH: source 1
> > [43015428.110000] drivers/pps/pps.c: New message from PID 23071 (flags 0)
> > [43015428.110000] drivers/pps/pps.c: PPS_FETCH: source 1
> > that means that process 23071 (ntpd) is fetching the pps.
> Yes. Those messages means that process 23071 is fetching PPS events.
Why is it then that it stays like this:
remote refid st t when poll reach delay offset jitter
==============================================================================
PPS(0) .PPS. 0 l - 64 0 0.000 0.000 0.001
(ntpq -c pe)
Folkert van Heusden
--
www.vanheusden.com/multitail - win een vlaai van multivlaai! zorg
ervoor dat multitail opgenomen wordt in Fedora Core, AIX, Solaris of
HP/UX en win een vlaai naar keuze
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
More information about the LinuxPPS
mailing list