Re: high precision tracking: trying to understand sudden jumps

David Woolley schrieb:
Bill Unruh wrote:
On Sun, 30 Mar 2008, starlight@xxxxxxxxxxx wrote:


You appear to be quoting an off list reply with no indication of permission, although it is just possible that the email gateway forwarded it to email subscribers without forwarding it to the usenet group proper.

Incidentally, what he's done is to run together the peers information from many machines, so there is only one CDMA source. On the other hand, it doesn't look like it is a CDMA appliance, or if it is, it has been badly implemented, as I would not expect to see a local clock driver on an appliance device.

We have that in our NTP appliances as well. You can configure it to any stratum level you want and it is used as a last resort fallback in case the receiver lost reception and the (also configurable) so-called trust time has passed without the signal coming back. This results in the time server replying with stratum 12 (for example) after a while and ensures that everybody has the same time, although it might be wrong. If a user does not want that, they can simply set the local clock stratum to 15 and the server will not be accepted anymore.

Can you please let me know why you consider this a "bad implementation"?

Regards,
Heiko

[...]
.

Relevant Pages

  • Re: Too high steps in time reset
    ... never going to be used as the server of record, ... The DCF server worked good for 8 years, syncronizing my ntp server ... number of LOCAL clock sources that you have. ...
    (comp.protocols.time.ntp)
  • Re: Cannot synchronize to server with local clock
    ... local clock, since the machine is always running, and used it as the clock ... server for my LAN. ... remember correctly, its stratum changed from 16 when unsynced, to one less ...
    (comp.protocols.time.ntp)
  • Re: Too high steps in time reset
    ... I was going to say that that never has valid time, but actually it is never going to be used as the server of record, even though it has valid time, because the local clock will always win. ... The DCF server is useless because of its stratum, and would be of questionable value because of the large root dispersions it will accumulate between updates. ...
    (comp.protocols.time.ntp)
  • Re: Cannot synchronize to server with local clock
    ... >> And AFAICS in ntpd a local clock driver will never change it's stratum ... > remember correctly, its stratum changed from 16 when unsynced, to one less ... tries to sync to another ref time source that is reachable. ...
    (comp.protocols.time.ntp)
  • Re: high precision tracking: trying to understand sudden jumps
    ... If a user does not want that, they can simply set the local clock stratum to 15 and the server will not be accepted anymore. ... Basically, when it falls back to the local clock, root dispersion goes to zero, when the true situation is that root dispersion is growing without bound. ...
    (comp.protocols.time.ntp)