I need to be able to start a service only after time synchronization has
occurred. I implemented this as a systemd target with ntpd and ntp-wait
but I can't find an equivalent for timesyncd. I found a couple references
to this problem but didn't find them helpful:
* [Patch from 2014]
https://list
Hi all,
I have a small device MicroUPS which helps me to shutdown my system on
embedded devices, it is controlled by script /etc/init.d/microups and in this
script I need to know whether system is going down for reboot or for halt,
because in case of halt I need to send small data over RS232 to
08.08.2017 17:03, Marek Floriańczyk пишет:
>
> What would be the proper way to distinguish between system is going down for
> reboot and for shutdown ?
>
Straightforward way is to make your service WantedBy poweroff.target and
halt.target. You can then have second service WantedBy reboot.target
Dnia wtorek, 8 sierpnia 2017 21:04:18 CEST Andrei Borzenkov pisze:
> 08.08.2017 17:03, Marek Floriańczyk пишет:
> > What would be the proper way to distinguish between system is going down
> > for reboot and for shutdown ?
>
> Straightforward way is to make your service WantedBy poweroff.target an
I suggest first porting microupsd itself to a native systemd .service file
(so that it'll have process monitoring and everything). That might even fix
part of the problem.
Normally services are given a certain amount of time to stop after SIGTERM
(or whatever KillSignal was set, or whatever ExecSt
Dnia wtorek, 8 sierpnia 2017 19:35:12 CEST Mantas Mikulėnas pisze:
> I suggest first porting microupsd itself to a native systemd .service file
> (so that it'll have process monitoring and everything). That might even fix
> part of the problem.
Hi
I have no problem with changing some code in micr