Short question:
How do I make xntpd continue to report itself to clients as a usable
stratum 3 server even when it has lost sync with its stratum 2 references?
Longwinded form:
I have a LAN on which only one Linux system is connected to the Internet
(I know how to setup an IP-Masq firewall, I just don't want to) and since I
am using NFS and a few other things in which clock synchronization is a
real issue, I configured xntpd in an attempt to sync all the clocks on my
LAN, the problem I am now having is that my ISP's ISP has some routing and
packet loss problems from time to time, so the machine which is connected
to the 'net is sometimes unable to talk to any of the stratum 2 NTP servers
it normally sync's with, and as soon as it goes out of sync it starts
reporting itself as stratum 16 instead of stratum 3, which appears to cause
all the other machines on the LAN to stop attempting to sync their clocks
to it. I am far more interested in having all the machines on the LAN think
that it is the same time (to as fine a tolerance as I can manage) than in
insuring that the time is "correct" UTC, and I'm told that I can use a
"fudge" line in my ntp.conf to force the connected machine to report itself
as a usable stratum 3 server even when it is temporarally out of sync, but
I have not been able to find any documentation of it. Does anyone know how
to do this?
--
The difference between genius and stupidity is that genius has its limits.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
