A C wrote:
On 3/29/2012 03:29, David Lord wrote:
Dave Hart wrote:
On Thu, Mar 29, 2012 at 02:44, A C agcarver+...@acarver.net wrote:
Without flag3 it appears that ntpd does the heavy lifting but is
unable to
use the PPS unless a prefer peer is set. With flag3 enabled, PPS is
running
without a
update status for yesterday test:
#ntpq -p
remote refid st t when poll reach delay offset jitter
==
xGPS_NMEA(1) .GPS. 0 l 5 8 377 0.000 -256.03 3.906
xtb.mircx.com
David Lord wrote:
A C wrote:
On 3/29/2012 03:29, David Lord wrote:
Dave Hart wrote:
On Thu, Mar 29, 2012 at 02:44, A C agcarver+...@acarver.net wrote:
Without flag3 it appears that ntpd does the heavy lifting but is
unable to
use the PPS unless a prefer peer is set. With flag3 enabled, PPS
On Fri, Mar 30, 2012 at 12:44, G gen...@yahoo.com wrote:
root@test12041:/home/ntp-4.2.6p5# ntpq -p
remote refid st t when poll reach delay offset jitter
==
xGPS_NMEA(1) .GPS. 0 l
G wrote:
update status for yesterday test:
#ntpq -p
remote refid st t when poll reach delay offset jitter
==
xGPS_NMEA(1) .GPS.0 l58 3770.000 -256.03 3.906
On Fri, Mar 30, 2012 at 15:58, David Lord sn...@lordynet.org wrote:
If you need to use 127.127.22 driver I'd suggest to use ntpd
v4.2.6p3. I don't know if parallel port pps works with the type
20 driver.
It does as long as /dev/gpspps0 (or whichever unit number) is linked
to the correct device
