> -----Original Message----- > From: questions- > bounces+edward.mischanko=arcelormittal....@lists.ntp.org > [mailto:questions- > bounces+edward.mischanko=arcelormittal....@lists.ntp.org] On > Behalf Of unruh > Sent: Tuesday, December 11, 2012 1:36 AM > To: questions@lists.ntp.org > Subject: Re: [ntp:questions] NTP_MAXCLOCK in ntp.h > > On 2012-12-11, Mischanko, Edward T > <edward.mischa...@arcelormittal.com> wrote: > > Please tell me why when watching my client with NTP Time > Server Monitor by Meinberg, my client does not honor the > NTP_MAXCLOCK setting in the ntp.h file. > > > > Why do you thing your client does not honour that setting? And > what do > you think this setting does? > > _______________________________________________ > questions mailing list > questions@lists.ntp.org > http://lists.ntp.org/listinfo/questions [Mischanko, Edward T] I believe the setting limits the maximum amount of peers that are selected as candidates for averaging?
/* * Selection algorithm tuning parameters */ #define NTP_MINCLOCK 3 /* min survivors */ #define NTP_MAXCLOCK 10 /* max candidates */ #define MINDISPERSE .001 /* min distance */ #define MAXDISTANCE 1.5 /* max root distance (select threshold) */ #define CLOCK_SGATE 3.0 /* popcorn spike gate */ #define HUFFPUFF 900 /* huff-n'-puff sample interval (s) */ #define MAXHOP 2 /* anti-clockhop threshold */ #define MAX_TTL 8 /* max ttl mapping vector size */ #define BEACON 7200 /* manycast beacon interval */ #define NTP_MAXEXTEN 2048 /* max extension field size */ #define NTP_ORPHWAIT 300 /* orphan wair (s) */ /* _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
