On Wed, Mar 23, 2022 at 3:22 PM Miroslav Lichvar wrote:
>
> On Wed, Mar 23, 2022 at 03:15:21PM +0300, Andrei Borzenkov wrote:
> > And systemd-timesyncd.target will pull in time-set.target:
> >
> > Wants=time-set.target
> > Before=time-set.target
>
> An impor
On Wed, Mar 23, 2022 at 2:28 PM Krix Rosinski wrote:
>
> Hello all, thank you for the speedy reply!
>
> @Laura, yes we disable systemd-timesyncd completely and enable chrony instead.
>
> @Kevin, I may ask a separate question there, I thought this will be a common
> issue for chrony users though.
hrony/drift
> makestep 1.0 3
> rtcfile /var/lib/chrony/rtc
> rtconutc
> rtcautotrim 30
>
> You also asked:
> "Is your board shut down when it gets power failure indication or it is
> simply switched off?"
>
> It is just switched off, no shut down in case
On 11.09.2021 13:02, Uwe Fechner wrote:
> Hello,
>
> we have an Linux ARM board that can be connected to the internet
> using a wired connection.
>
> Chrony is started at boot time.
>
> After a power failure it can happen that our board starts up BEFORE
> internet becomes available, for example
Chrony comes with sample NetworkManager dispatcher script that offlines
NTP sources when interface goes down and onlines them when interface
comes up. Technically it runs "chronyc onoffline" which tries to
determine whether each source can be reached. This script is actually
installed by
