| 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: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Subject: Re: [chrony-users] Re: Linux time goes wrong after changing the time with 'date' cmd
- From: Feng Tang <feng.tang@xxxxxxxxx>
- Date: Mon, 13 May 2024 16:16:04 +0800
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=intel.com; dmarc=pass action=none header.from=intel.com; dkim=pass header.d=intel.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=Aj4e/W9gRXebJIg7rq72PjiwuZXTNIvkEwEjYs6VQbk=; b=K5ISsz6AugBcM3iiKkbFdpHBoVxb+mOLvSQo6C9yzHUJ6ZYs1A5475mfgJCyPDpryZkHYKEbYIfBqkqCaMxl3h6FkSlmvZ8TlAAKARdNUo/ZOo3QU0JB2gwz20gMUDeHDXJIsN2LnJEcl4DMdP2eA8tHniYqVMDFa8+X2vEX/zOsPPznSuTz7n+hQJd60uuXC9s+57rRYrKQ+otCEl3XpvPnZoYSVlwvjAHbZJW5b9vJPbmob1FoPKfPTy97sj93oISiO+8pVf13ffZE7EE6TPLmmZPiBpBflPtQZa6U4DAXahzOPFjJ38S0mHjIT7/k7xOSpjHHcDgoWvuP7PRlPA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZVePdi9PmP/Yu+unNfm6HutSUt2HrApWyjEIMbJXNV01aPkWB5Nz1hRRhm0QBjyvKjRP1YbHnzpfajMOCC73NDa5TmspdbCt0qFBSVv4XH9k491h+nqE4tAEuQGBU1zVFZ8LFrOtSVvOUAlsNusNskaxD7CpIZ+OT6yrS1KADoTgdk24UVVkxZ7LYF3X20CWmaZgCLYRHvXBGhMjvyFO9a4h47iDsC/GQjIDNSxjejsm9MPcQpM4oRJ484bCyBd0sKg2rtoMJtgHgPUN5EqltNcujzPxZ74ZAcw1lO25GIButWcmw0Yc72EsfiFnn4DsEtGdzOE1yHexV+MySf6hEQ==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=intel.com;
- Cc: <chrony-users@xxxxxxxxxxxxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1715589065; x=1747125065; h=date:from:to:cc:subject:message-id:references: in-reply-to:mime-version; bh=Aj4e/W9gRXebJIg7rq72PjiwuZXTNIvkEwEjYs6VQbk=; b=CgxbYd2ZDvIJdG0QOYBpmF5zhh24uE8uMVj2I7+i2tZghCALX6xA/Dl7 pC5dP6Nh0vCZav7iIscrHUgLskeSYKVjcotLFENeBvRF+jF7s4Hy7AU3O LHBzx5oU7P1fPX0FBJQQZsj1WTIxBi+dhV0wvGouMJIa6iaOuL7ATz62f NYCINCLDxQuIVr/Y4WpwUCs/63DKGhNTS2T3OhIgCKVZuoGcO1cptVyPt XWiVy8/JRIVaK5xLun5henkXufHpcoBDW5cDQowN4zF0yLgfmOzEaLuFY J+8kPH22E6kELrVnBjFVfj6umxnYr7Uq1qn48ARpjtehVubMyV0eonsZL w==;
Hi Miroslav Lichvar,
On Mon, May 13, 2024 at 08:19:07AM +0200, Miroslav Lichvar wrote:
> 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.
Yes, exactly. In the above case, we saw the system time was compensated
very slowly.
>
> 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
This works great in my test and the issue can't be reproduced. Many
thanks for the hint!
- Feng
>
> --
> 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.