On Sat, Apr 25, 2020 at 2:19 AM Andrei Borzenkov wrote:
>
> ps.service does not call any script on startup.
> >
> > 1) psd.service remains in an active state
> > 2) psd-resync.timer remains active
> >
> > I'd like:
> > 1) both psd.service and psd-resync.service to both end in an error state.
> >
Am Sa., 25. Apr. 2020 um 08:52 Uhr schrieb www :
> Apr 02 17:24:52 demoboard systemd[1]: System time before build time,
> advancing clock.
See https://github.com/systemd/systemd/blob/master/src/core/main.c#L1485
or more specifically
hi Michal & Kevin,
I find that just shutting down *timesync* service can't solve the problem.
Build time also affects system time.
My testing process is as follows:
1. systemctl disable systemd-timesyncd
systemctl mask systemd-timesyncd
2. timedatectl set-time "2001-11-30 17:36:46"
24.04.2020 16:57, John пишет:
> I'd like to have systemd (user mode) call a bash script with different
> tokens under two conditions:
> 1) When the user starts/stops a service (token would be either "sync"
> or "unsync")
> 2) When a timer tells it to run (token would be "sync")
>
> Thus far, I
