| Re: [chrony-users] Re: Linux time goes wrong after changing the time with 'date' cmd |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: Feng Tang <feng.tang@xxxxxxxxx>
- Subject: Re: [chrony-users] Re: Linux time goes wrong after changing the time with 'date' cmd
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 13 May 2024 08:19:07 +0200
- Cc: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1715581176; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=zePQaJ/yt1lGfR5taxDLBImMMinJCoRRzMNBqt2lBaI=; b=dgrBNt/+4Avj+qUq4L7lm9ffWcBnlJ4HOeQLmV7lpsdm6Ov1e/6VGxgFLcZYulIMwQJ0G5 0QUh2POtEGRMO2zyNP1UXjNqyjYeJOEesPYAJNTAYjLXh76o2moq7Jn0rzBkYGzB3H44l3 HkRgchumMZWArNBBNjClVQwgvFFwEqo=
On Mon, May 13, 2024 at 09:02:31AM +0800, Feng Tang wrote:
> So my thought is, since user already chose to trust 'chrony', and
> when chrony has more realiable NTP time source, 'chrony' can help to
> correct the 'wrong date' set by user with the right time, practically
> 'rejecting' the huge time jump set by users.
chronyd is trying to correct the clock, but a typical default
configuration provided with distro packages allows steps only on
start, so the ~10% slew can take very long time.
The user would need to allow steps at any time. See this answer in
the FAQ:
https://chrony-project.org/faq.html#_is_chronyd_allowed_to_step_the_system_clock
--
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.