| Re: [chrony-users] Resume from suspend and default makestep configuration |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: "chrony-users@xxxxxxxxxxxxxxxxxxxx" <chrony-users@xxxxxxxxxxxxxxxxxxxx>
- Subject: Re: [chrony-users] Resume from suspend and default makestep configuration
- From: FUSTE Emmanuel <emmanuel.fuste@xxxxxxxxxxxxxxx>
- Date: Mon, 18 May 2020 10:45:02 +0000
- Accept-language: fr-FR, en-US
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thalesgroup.com; s=xrt20181201; t=1589798703; bh=I+PPkESH9jZOWJ8fpYorR/0JWmcAOAStcs6cxFGGk4Y=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Transfer-Encoding:MIME-Version:From; b=mKJetQ/aP/Uk2H+7jxn4V+gOdOxMHjoMVEwe0kKCgOnuHQcw8IUX0FBpmQaIe79c5 nXzVnMu3he3lvBCwWiEj7tJwejPXbXVFgXJPzrMec5rStoh/r+boopRZVKmpC1uWrH +uBVNXiASG2CJDAoBNUBpRvqyFrKr3CwttuTX6JC3VZgPFeGox3X31pT2RVFeVrceC x1SV4jDmr84lW0m0G04VFi/JvMe8uzm1mDhG5agLxgBkif258Zd505k2VyF1koCMI1 q+hpt4/ZmjGtjl1iVOMq56rUbcSy9QFrsZOew5S2HnSscYgQ0GQZYPO1sEQtkXoL8A vVVDVAhthyE3Q==
- Thread-index: AQHWJZCybs6tsl5rVkeZuk2veTx73Kiidm+AgAsddICAAAI2AA==
- Thread-topic: [chrony-users] Resume from suspend and default makestep configuration
Hello Pali,
Le 18/05/2020 à 12:37, Pali Rohár a écrit :
> The main problem is when system is put into suspend or hibernate state.
>
> In my opinion resuming from suspend / hibernate state should be handled
> in the same way as (re)starting chronyd. You do not know what may
> happened during sleep.
Yes and in case of needed workaround, it should be done at the system
level, not chrony.
A job for systemd.
> And as I pointed there are existing problems that UEFI/BIOS firmware
> changes RTC clock without good reason which results in completely wrong
> system clock.
>
Could well be identified by blacklist at the udev/systemd level for
applying or not the workaround (restart chrony or launch a chronyc
command at resume)
Emmanuel.