In article <[EMAIL PROTECTED]> "Richard B. Gilbert" <[EMAIL PROTECTED]> writes: > >If you MUST serve your local clock, "fudge" it to stratum 10 like this: ># ># Declare the local clock to be the clock of last resort. ># It will be used to serve time in the absence of any other. ># >server 127.127.1.0 # Local clock, unit 0 >fudge 127.127.1.0 stratum 10
Agreed (but probably not useful if the server is w32time or whatever it's called). >Your client does not believe the server because the server is serving an >unsychronized local clock that has NEVER been synchronized. The client has no way of knowing that, at most it can tell that the server is using a particular kind of refclock - it could even be a perfectly "NTP-legitimate" setup if the local clock is disciplined by some other means. I.e. in general, it works just fine to use NTP to synchronize against a server that only has its local clock as reference (the quality of the time is another thing) - according to the docs it's even "the intended use" for the LOCAL refclock, and of course it's quite commonly done. The problem here is with the server (non-)implementation. --Per Hedeland [EMAIL PROTECTED] _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
