Perhaps my statement was ambiguous, here's a next try. Although in the
meanwhile we found the culprit and it's NOT ntp, I still consider it
worth to post the solution as others might experience similar problems.
Sorry for the noise.
Our Setup: Stand-alone (Ubuntu) Linux desktop computer, GPS/PPS c
On 12/06/15 11:54, Joachim Fabini wrote:
> The straight-forward solution that you propose was the one that I tried
> first. Unfortunately it does not work.
Then I guess I don't understand what you're after exactly. I'll re-read
your message entirely and check what I misunderstood. Sorry for the no
The straight-forward solution that you propose was the one that I tried
first. Unfortunately it does not work.
But we might have found one (the?) solution: Build ntp from sources and
replace the line
#define HAS_ROUTING_SOCKET 1
by
#undef HAS_ROUTING_SOCKET
in configure.h (_after_ running configur
On 12/06/15 10:07, Joachim Fabini wrote:
> I want ntp to listen exclusively to the local GPS/PPS
> signal (server 127.127.20.0) and ignore all other network interfaces,
> messages, events
Use the interface directive, e.g.:
interface ignore all
interface listen 127.127.20.0
Ciao
-- bronto
__
Does anyone know how to stop ntpd to listen to local network interface
changes? That is, I want ntp to listen exclusively to the local GPS/PPS
signal (server 127.127.20.0) and ignore all other network interfaces,
messages, events, etc.
Background:
I'm using ntp on a Linux-based box for accurate ti