[LinuxPPS] NMEA and NTP

[Paul]

Thanks Udo, I've modified my ntp.conf to suit. davehart you are right as
well, but something is still odd.... I changed the peer name from
myserver.mydomain to 192.168.1.1 and it worked. But in the peers list it
is listed as myserver.mydomain (so reverse DNS is OK). Forward DNS works
perfectly outside of ntp (ping myserver.mydomain). So forward dns is not
working inside ntp - very odd.

On Mon, 2010-05-31 at 18:30 +0100, Paul wrote:
> On Mon, 2010-05-31 at 19:00 +0200, Udo van den Heuvel wrote:
> > On 2010-05-31 18:49, Paul wrote:
> > > But I cannot add an external
> > > peer. When I do so, 2 ntpd processes are started, but I only see the
> > > NMEA source when I do ntpq -p. Wierd. And with external sources only,
> > > still two ntp processes are started but there are no references in ntpq
> > > -p The ntp also does not appear to write to a driftfile even though I
> > > have specified it in ntp.conf
> > 
> > On #ntp davehart mentioned:
> > 
> > sounds like his DNS isn't working.  the two ntpd processes are because
> > one is trying to resolve DNS names.
> > 
> > _______________________________________________
> > LinuxPPS mailing list
> > LinuxPPS at ml.enneenne.com
> > http://ml.enneenne.com/cgi-bin/mailman/listinfo/linuxpps
> > Wiki: http://wiki.enneenne.com/index.php/LinuxPPS_support
> 
> Thanks Udo, I've modified my ntp.conf to suit. davehart you are right as
> well, but something is still odd.... I changed the peer name from
> myserver.mydomain to 192.168.1.1 and it worked. But in the peers list it
> is listed as myserver.mydomain (so reverse DNS is OK). Forward DNS works
> perfectly outside of ntp (ping myserver.mydomain). So forward dns is not
> working inside ntp - very odd.