| [chrony-users] Kernel time sync flag (on Linux) and chrony |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-users] Kernel time sync flag (on Linux) and chrony
- From: Watson Ladd <watson@xxxxxxxxxxxxxx>
- Date: Wed, 19 Jun 2019 11:55:51 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=tc7oK88V6pFL6jFyV9ZMd6YVtJXNXCn2dcxAFXfbhwk=; b=PpqDv2t+mwRSUY2Kq8T0BBvuvi37XUwyk/5O6aCgt/9d7QR7VhSL7LvlaEpfNgPo41 qz//o9kGsoXEOlwWHnopE23I1NmgKxReNygWviJlLJR7yxf7OGYi9YKUhuRXEZ/J/BET Kz2hAxzyR67tyZIV7vS0a6U+iAc7tKsw/vamA=
Dear fellow users,
Since switching to chrony we've seen that the kernel's timex
sync_status flag occasionally becomes unsynced, while chronyd is
happily running and synchronizing the time acceptably. Unfortunately
we had an alert based on this back when were using ntpd.
Can anyone shed light on how chronyd sets the sync_status flag when
running and why it might not update the kernel as frequently as ntpd?
Sincerely,
Watson Ladd
--
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.