| Re: [chrony-users] Chrony not taking SOCKET data from Application |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Chrony not taking SOCKET data from Application
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 28 Mar 2023 13:03:31 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1680001415; 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=U7rPPKbfco5pXtSV6CwbbRE0CIbMBIYVwdSSUdpg0VY=; b=RtBZpPJNYUb8QZbq0OIpQru0E89s1/GYw4a1hTRj0eA8ay8K6g8e/vFBCxJD7Bwwyx45/K 6/s7kMO+VnhY1rawORdolSZUlJAt8NaRRoWuzCn7yEcZfugjQfqbKr9WI5QJduJW3mlG0o Nae/OhR/lDWn6NIyWo1Pcjh05nCImto=
On Tue, Mar 28, 2023 at 04:17:21PM +0530, sarveshwar k wrote:
> I have attached a screenshot of my observation. When the current time is
> 4:11:17, the Ref time is 4:11:15 (as mentioned in tracking output).
> [image: image.png]
This is similar to the LastRx issue you reported before. The timestamp
is intentionally adjusted by a small random value to make it more
difficult to predict receive timestamps in the NTP symmetric mode.
It's not necessary with a reference clock, but it's simpler do it
always.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.