| Re: [chrony-dev] Adding information to tracking |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] Adding information to tracking
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Thu, 26 Oct 2023 14:54:53 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1698324901; 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=hpWCvMMAm3C59Ff905bIiziIJI34l6o1EpHxu3HzQhg=; b=MCfSuhDoGhZRp2i3v+GIi2q3VPkaHSyXAcoLFqn/qf+R3PZ7T2ZumyhYicgxLKBfR70TId qo9g0sz9f6KHmjb1FA5kNkGifE/Meh+vwfhKGLslDeLg+MtINSkQPE2+1L/HvpL5qWtQ3y j4Gs3ZsNTQ6IAiowqxOPXZIp7/651LI=
On Wed, Oct 25, 2023 at 06:07:04PM -0400, Jonathan Sanabria wrote:
> In my current monitor for steps we would have to track the machine's system
> time and check for jumps like that, though parsing the tracking information
> would be much safer and direct.
Why not check the system log for the "System clock was stepped"
message?
If the last step was reported in tracking, you wouldn't know if there
wasn't a bigger step since the previous chronyc tracking call as steps
can happen in quick succession if there are changes in the source
selection.
Also, it's not very clear to me why you care about steps but not
larger slews. If you need to know if the maximum estimated error of
the clock is below a specific value, you should be monitoring the last
field in the tracking.log file.
--
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.