Hi,
With a working wlan/lan bond0 failover, how can we trigger other
local services whenever a failover happens?
Why: In our case, a local openvpn client service needs SIGUSR1
whenever the own IP address changes, after a failover. See man
openvpn(8), --ipchange.
The problem: After a failover, th
You could use the networkd-broker tool (or its predecessor
networkd-dispatcher) to react to networkd's configuration events, or a
netlink-based tool (similar to `ip mon addr`) to directly watch IP address
changes.
To be honest though, a bond0 that's connected to two completely different
networks k
On Thu, Sep 29, 2022 at 9:41 AM Ulrich Windl
wrote:
>
> >>> Andrei Borzenkov schrieb am 28.09.2022 um 20:34 in
> Nachricht :
> > On 28.09.2022 09:25, Ulrich Windl wrote:
> >> Hi!
> >>
> >> I'm trying to establish a mechanism that uses a generator-like mechanism as
> > described below. Unfortunate
grawity:
> You could use the networkd-broker tool (or its predecessor
> networkd-dispatcher) to react to networkd's configuration events, or a
> netlink-based tool (similar to `ip mon addr`) to directly watch IP address
> changes.
Thanks! So it seems there is no pure systemd way to get triggered.
>>> Andrei Borzenkov schrieb am 29.09.2022 um 13:57 in
Nachricht
:
...
>> I don't quite understand what an "initial transaction" is,
>
> The set of (start) jobs starting with default.targtet (or whatever
> target was given to systemd as "initial target") and following
> dependency chain (Wants an
On Thu, Sep 29, 2022 at 4:01 PM Ulrich Windl
wrote:
>
> >>> Andrei Borzenkov schrieb am 29.09.2022 um 13:57 in
> Nachricht
> :
> ...
> >> I don't quite understand what an "initial transaction" is,
> >
> > The set of (start) jobs starting with default.targtet (or whatever
> > target was given to s
Thanks for your answer.
After some research, it seems that issue is already registered and fixed :
https://github.com/systemd/systemd/issues/23410
BR,
Eric
-Message d'origine-
De : systemd-devel De la part de
Colin Guthrie
Envoyé : mercredi 28 septembre 2022 18:18
À : systemd-devel@
Hi,
sorry in advance if I'm posting to the wrong list. I need to run systemd
inside a docker container and attach it to the container's stdin/stdout.
The reason for this weird request is the following:
1) I need to use the container for running Gilab CI jobs
2) the software being tested needs
