| Re: [chrony-users] Add configuration option to disable randomized transmit timestamp |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Add configuration option to disable randomized transmit timestamp
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 27 Sep 2021 08:58:13 +0200
- Authentication-results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1632725900; 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=svh5ER30WJ7plgX9GZvURQpQQvX329GQBPusENbYyvM=; b=PyVCqp/z83J7ljpbdRw7PN/rLyrwCHbcGzeee+nWfYwbB609jC4Xk0eRdkfiIDLZRT1Tan ofeJuHee+mj7XM1NSssHuIKxrViP7NCuDyLhZS9/FINbVBcLT5pO8rGLJTa6Iu/K7Sm/3A m/Rf+788Z5Ew7hoWSvhV6ImvYzHrMEE=
On Mon, Sep 27, 2021 at 01:41:39PM +0800, egg car wrote:
> In the scenario of local datacenter, we've been monitoring client system
> time quality by logging transmit timestamp in clients ntp requests on NTP
> server.
> But this seems not working correctly when we're using chrony instead of
> ntpd on some machines.
> I know this is a default 'feature' of chrony, but should we have a switch
> to turn off this behavior?
You can configure the clients with the peer directive instead of
server directive to disable the transmit timestamp randomization.
A better way to monitor the clients would be to enable them as NTP
servers and specify them as servers with the noselect option on the
monitoring node. This way you would get a better estimate of their
error, compensated and filtered for the network delay.
--
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.