Hallo all!
I'm working on an embedded project consisting of an host and numerous virtual
machines and am facing problems related to time management. systemd-timesyncd
dies on one machine (HOST), but runs okay on another (VM2) with identical
config.
The project setup is as follows:
HOST: Runs
Sorry, some typos. The time server is VM1, not VM3.
Please find a corrected version below.
~~~
Hello all!
I'm working on an embedded project consisting of an host and numerous virtual
machines and am facing problems related to time management. systemd-timesyncd
dies on one machine
On Mon, Sep 3, 2018 at 3:41 PM Manuel Wagesreither
wrote:
> Hallo all!
>
> I'm working on an embedded project consisting of an host and numerous
> virtual machines and am facing problems related to time management.
> systemd-timesyncd dies on one machine (HOST), but runs okay on another
> (VM2)
Hi,
Doesn't anybody experienced the same issue with systemd-journald ?
Best regards,
Frédéric HILPERT
On 20/08/18 14:08, Frédéric HILPERT wrote:
Hi,
I have a question about systemd. Not wanting to create an issue on
githbub because there are already plenty and this may not be a bug.
I
You can put multiple criterion in a single .timer
In your case, combining OnBootSec and OnUnitActiveSec should do what you
want...
HTH
Jeremy
On 03/09/2018 17:28, Wojtek Swiatek wrote:
Hello everyone
I would like to have a timer which runs every 60 seconds after the machine
is booted.
I
Hello everyone
I would like to have a timer which runs every 60 seconds after the machine
is booted.
I thought that OnBootSec would be the right parameter but this is s a one
shot call - it starts 60 seconds after the boot and then the service is
done (does not restart ever)
Is there a way to
Le lun. 3 sept. 2018 à 17:30, Jérémy Rosen a écrit :
> You can put multiple criterion in a single .timer
>
> In your case, combining OnBootSec and OnUnitActiveSec should do what you
> want...
>
>
Thank you - that was it.
OnBootSec=60s
OnUnitActiveSec=60s
I did not realize that OnUnitActiveSec
