Hiya,
As has been said, this is racy. "Sufficiently early" is just a hope,
rather than a guarantee. Perhaps something in the kernel made things
more or less efficient (try booting with the old kernel to see if it
helps, but as this is a race, it may only work some of the time.). Or
perhaps so
Hi,
I have created a systemd script along with the timer which runs once every
three hours. I have the same settings across node1 and node2 which are
hosted behind the load balancer. The reason setting behind LB is to make
sure we avoid a single point of failure scenarios. I have a specific issue
Heya!
Currently systemd doesn't have this kind of distributed scheduler . Though
I think it would be very interesting to explore (systemd-distributed seems
to be a fun name).
At some point coreos had a distributed version of systemd that did sort of
exactly what you want https://github.com/coreos
How to configure this service so that it will not automatically exit
Hello,
Thank you for your reply.
I can understand that there can be race.
*But when I check logs, there is no race happening*.
*Let us see and analyze the logs.*
Stage 1:
System boots, and kernel assigns eth0, eth1 and eth2 as interface names.
Aug 18 09:17:13 kk kernel: e1000e :00:1f.6 e
>>> Michael Chapman schrieb am 17.08.2021 um 02:52 in
Nachricht <885331af-bb7-41d0-e8-26c92023b...@very.puzzling.org>:
> On Tue, 17 Aug 2021, Dave Close wrote:
>> I'm trying to run "systemctl show" in a cron script. It works but I get
>> a huge number of extra lines in my log for each run. Why? Ca
On Wed, 18 Aug 2021, Ulrich Windl wrote:
> >>> Michael Chapman schrieb am 17.08.2021 um 02:52 in
> Nachricht <885331af-bb7-41d0-e8-26c92023b...@very.puzzling.org>:
> > On Tue, 17 Aug 2021, Dave Close wrote:
> >> I'm trying to run "systemctl show" in a cron script. It works but I get
> >> a huge nu
Hello
Further to my previous email:
I see that there is already an *extremely similar issue* reported on
July 12, 2021 and it has been fixed.
https://github.com/systemd/systemd/issues/20203
But I do not know if this fix exists in systemd v249.3 (Arch Linux)
If it exists that means that fix
