[ntp:bugs] [Bug 3594] ntpd discards messages coming through a nmead process and does not synchronize

bugzilla-daemon at ntp.org bugzilla-daemon at ntp.org
Thu Jun 13 06:28:25 UTC 2019


http://bugs.ntp.org/show_bug.cgi?id=3594

Juergen Perlinger <perlinger at ntp.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |CONFIRMED
                 CC|                            |perlinger at ntp.org
     Ever Confirmed|0                           |1

--- Comment #1 from Juergen Perlinger <perlinger at ntp.org> 2019-06-13 06:28:25 UTC ---
The NMEAD support is mostly unmaintained these days... and leaves quite a few
things to be desired.

Right now it is based on the assumption that the pause between incoming records
is so long that the input handler can actually read a line with each input
cycle. And that's a very sloppy decision for a stream socket.

I never used NMEAD, but if you're willing to do some testing we might get that
beast working again. But seriously, the GPSDJSON driver to attach to GPSD
instead of NMEAD would be a much better way, because GPSD provides timing
information that keeps the transmission delay between GPSD and NTPD out of the
equation.

But we have to fix bug 3593 first, because that affects everything.

-- 
Configure bugmail: http://bugs.ntp.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the bugs-announce mailing list