At 02:54 PM 1/24/00 -0500, Michael H. Warfield wrote:
>] server 127.127.1.0 # local clock
>] fudge 127.127.1.0 stratum 0
I read this, it's "close" but solves the wrong problem. I do have upstream
servers available 99% of the time, it's just that whenever a little bit of
packet loss
On Mon, Jan 24, 2000 at 03:11:48PM -0400, Chris Watt wrote:
> At 01:53 PM 1/24/00 -0500, Michael H. Warfield wrote:
> > Buy a GPS receiver and set up your own Stratum 1. :-)
> This is not a useful solution because:
Well... I was being "partially" facious (note smiley).
> 1. The m
At 02:35 PM 1/24/00 -0400, Chris Watt wrote:
>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?
If you include the following lines in /etc/ntp.conf
server 127.127.1.0
At 01:53 PM 1/24/00 -0500, Michael H. Warfield wrote:
> Buy a GPS receiver and set up your own Stratum 1. :-)
This is not a useful solution because:
1. The machine has no free I/O ports or IRQ's thus I would need to buy
another computer just to use as an NTP server, throwing out existing
On Mon, Jan 24, 2000 at 02:35:56PM -0400, Chris Watt wrote:
> 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 s
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