Re: [chrony-users] Resume from suspend and default makestep configuration

[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-users Archives ]


On Monday 18 May 2020 10:45:02 FUSTE Emmanuel wrote:
> 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.

Hello! Sorry for a stupid question, but what has systemd in common with
chronyd? Why should systemd care about chronyd time synchronization?

> > 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)

Could you describe in details what do you mean by blacklist? Which udev
blacklist you mean and what should be put into that blacklist? I have
not caught this part.

-- 
Pali Rohár
pali.rohar@xxxxxxxxx

-- 
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.


Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/