On 13 avr, 08:42, "David J Taylor" <david-
[email protected]> wrote:
> > ntpq -p
> > remote refid st t when poll reach delay
> > offset jitter
> > ==============================================================================
> > *ntpgmtaceb .1PPS. 1 u 20 64 377 0.144
> > -0.373 0.863
>
> > So it's seems to be really better, isn't it?
>
> If that is good enough for you, then the problem is solved. On my own
> LAN, where I wanted to improve the performance of the Windows-based NTP
> clients, I reduced the poll interval in the ntp.conf:
>
> server ntpgmtaceb iburst maxpoll 5
>
> This will make the client contact the server once every 32 seconds (2^^5),
> but that's no great load on either server, LAN or client. The "iburst"
> will speed up the initial sync.
>
> Cheers,
> David
After one night, the delay is 29.626
remote refid st t when poll reach delay
offset jitter
==============================================================================
*ntpgmtaceb .1PPS. 1 u 406 1024 377 29.626
0.867 1.231
if I put the line:
server ntpgmtaceb iburst maxpoll 5
ntpq -p:
No association ID's returned
If I run
ntpdate ntpgmtaceb
and I restart ntpd
delay is 0.169:
remote refid st t when poll reach delay
offset jitter
==============================================================================
ntpgmtaceb .1PPS. 1 u 12 64 1 0.169
3.814 0.001
ntpdate seems to be better?
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
