| Re: Re: [chrony-dev] Issue about chronyd synchronize to local clock |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: Re: [chrony-dev] Issue about chronyd synchronize to local clock
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Thu, 25 Jun 2020 16:54:48 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1593096892; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=mc8kXvdeMImWZ2xu0Fm9uLqed4vScTBTiR5IitdDueg=; b=EPFoybOz5sMahijNcmk6+z6jV5IZfkbT1lQBHHgYP9F2OEtPd00DP7+MaOW1UHfgIlJlWn y/G3LmyCwY4gUA56JrEVE6FMARny0k8WhNgMqJbCzVOe532BSkjExhBbwa2IihvIw/mdam ImMomEIbGAbBrTkobCEu6BTBM2THz+s=
On Thu, Jun 25, 2020 at 10:44:29PM +0800, xqmeng80@xxxxxxxxxxx wrote:
> As the application runs on the NTP server machine, time on the machine is thinked accurate. I just can't figure out why synchonizing to itself will make
> the NTP synchronization status becomes No after several hours.
Because the NTP stratum will increase with each iteration in the loop
and the client will stop synchronizing when it reaches 16. Then
it will just drift and when the root dispersion is too large, the
clock will be considered "unsynchronized".
--
Miroslav Lichvar
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.