[ntp:questions] Re: Reach error codes
Richard B. Gilbert
rgilbert88 at comcast.net
Mon Jan 23 15:48:38 UTC 2006
SivaKumar Subramani wrote:
>When I execute the "ntpq -p" displays reach value for all the time
>source as 377.
>What it means? When this shall be set to proper value and system clock
>shall be sync'd.
> remote refid st t when poll reach delay
> 126.96.36.199 188.8.131.52 3 u 696 1024 377 199.74 -725421
> 184.108.40.206 220.127.116.11 2 u 691 1024 377 199.89 -726021
> 18.104.22.168 22.214.171.124 3 u 707 1024 377 199.75 -723621
>What could be the problem?
>Thanks in advance.
>questions mailing list
>questions at lists.ntp.isc.org
Start ntpd with the -g option. This will cause it to set (step) the
clock on a one time basis. This will get your clock within a few
milliseconds of the correct time before ntpd tries to synchronize it.
Without this option, ntpd can take hours or days to adjust your clock to
the correct time or, if your clock is off by more than 1024 seconds, it
will exit immediately (panic).
The reach value of 377 is an octal number (representing 11111111 in
binary). Each time a server responds to a poll, a 1 bit is shifted in
from the right hand side. If a server fails to respond to a poll, a
zero bit is shifted in. 377 is a good value; it means that the server
responded to the last eight requests. During startup, it should
successively display: 1, 3, 7, 17, 37, 77, 177 and 377.
More information about the questions