Re: [ntp:questions] strange behaviour of ntp peerstats entries.

2008-02-02 Thread Unruh
David Woolley <[EMAIL PROTECTED]> writes: >Unruh wrote: >> >> This is in the clock_filter algorithm. It selects the sample of the last 8 >> which has the lowest delay (suitably aged) If that sample is the most >Yes. That's what I am talking about. Specifically clock_filter in >ntp_proto.c. >

Re: [ntp:questions] strange behaviour of ntp peerstats entries.

2008-02-02 Thread David L. Mills
David, We are talking right past each other and are not having a productive discussion. Tge best choice for me is just to shut up. Dave David Woolley wrote: > David L. Mills wrote: > >> Guys, >> >> This is really silly. The Unruh agenda is clear. Should you choose to > > > I think you repl

Re: [ntp:questions] strange behaviour of ntp peerstats entries.

2008-02-02 Thread David L. Mills
Unrug, You are not accurately describing the ntpd clock filter. An accurate desciption would surely help the point you are making. Davde Unruh wrote: > Grian Utterback <[EMAIL PROTECTED]> writes: > > >>David J Taylor wrote: >> >>>Brian Utterback wrote: >>>[] >>> Which is why NTP prefers

Re: [ntp:questions] strange behaviour of ntp peerstats entries.

2008-02-02 Thread David L. Mills
David, Can we take a time out? Can you read the NTPv4 specification where it describes the system process? Our disussion would be much more productive after that. Dave David Woolley wrote: > David L. Mills wrote: > >> David, >> >> I don't know what you mean by "figure head", but this is proba

Re: [ntp:questions] why is my pool server's offset so bad

2008-02-02 Thread Pat Farrell
On Fri, 01 Feb 2008 02:33:09 +, Danny Mayer wrote: > You should at least upgrade to 4.2.4. The refid garbage on the line for > prometheus was fixed a long time ago. I just did. It was less trivial than I wanted, as the debian repositories get updated very slowly. 4.2.2. is the latest and grea

Re: [ntp:questions] strange behaviour of ntp peerstats entries.

2008-02-02 Thread David Woolley
Unruh wrote: > > This is in the clock_filter algorithm. It selects the sample of the last 8 > which has the lowest delay (suitably aged) If that sample is the most Yes. That's what I am talking about. Specifically clock_filter in ntp_proto.c. > recent, then it is actually used. Otherwise noth

Re: [ntp:questions] strange behaviour of ntp peerstats entries.

2008-02-02 Thread Unruh
David Woolley <[EMAIL PROTECTED]> writes: >Unruh wrote: >> >> Worse than that . Only if the latest sample is the one with the min delay >> is it chosen Otherwise it is not. You can go for 16 or more samples never >> using any of thembefor one fits the criteion. (actually the samples are >> aged

Re: [ntp:questions] strange behaviour of ntp peerstats entries.

2008-02-02 Thread David Woolley
Unruh wrote: > > Worse than that . Only if the latest sample is the one with the min delay > is it chosen Otherwise it is not. You can go for 16 or more samples never > using any of thembefor one fits the criteion. (actually the samples are > aged as well-- ie the delay is increased as they get o

Re: [ntp:questions] strange behaviour of ntp peerstats entries.

2008-02-02 Thread Unruh
"David L. Mills" <[EMAIL PROTECTED]> writes: >Guys, >This is really silly. The Unruh agenda is clear. Should you choose to >limit the application space to fast local networks, the chrony choice >may or may not be optimal. Should you extend this space to the raunchy >global Internet, conviction

Re: [ntp:questions] strange behaviour of ntp peerstats entries.

2008-02-02 Thread Unruh
Grian Utterback <[EMAIL PROTECTED]> writes: >David J Taylor wrote: >> Brian Utterback wrote: >> [] >>> Which is why NTP prefers the source with the smallest delay. The >>> system I am using has servers whose delays are 51ms to 94. I can't >>> find any closer. On my company LAN, the delays range fr

Re: [ntp:questions] Ultralink 325 WWVB receiver

2008-02-02 Thread Rob Kimberley
> You mean from Fort Collins? I'm about 1495 km from there. > > I'll generate some plots and post links to them in a few days, after > enough data has been gathered. I probably should have done that from the > beginning. Sorry - I meant Fort Collins (right State though!). Look forward to seei

Re: [ntp:questions] strange behaviour of ntp peerstats entries.

2008-02-02 Thread David Woolley
David L. Mills wrote: > Guys, > > This is really silly. The Unruh agenda is clear. Should you choose to I think you replied to the wrong node in the thread. I think what you are actually doing is telling Steve that he shouldn't be asking for these changes to included in ntpd at all. Also, I

Re: [ntp:questions] strange behaviour of ntp peerstats entries.

2008-02-02 Thread David Woolley
David L. Mills wrote: > David, > > I don't know what you mean by "figure head", but this is probably what I meant that it is the one peer chosen to represent all the peers actually used. > is intended. The statistics such as root delay, root dispersion and > related statistics are in fact inh