I have two systemd services
A (takes a few minutes) and
B (only very few seconds):
Ahas a high priority and must run under all circumstances.
Bcannot be started when
Aruns, but there is no problem to start
Bstill runs. It is even desired to start
Bstill runs, as
Amust run under all circumstances.
Bshouldn't be killed when
Conflicts=stops the service, instead it should still finish running.
The systemd man tells me:
Configures negative requirement dependencies. If a unit has a Conflicts= setting on another unit, starting the former will stop the latter and vice versa.
I thought using
Conflicts=A.service might be the solution. The man tells me that starting
A will stop
B, but also what I don't want is
B will stop
Is there a way to have
Conflicts= just unidirectional?