hard dependencies for systemd units about norns-image HOT 7 CLOSED

Also, maiden doesn't require either crone or matron to run, so it can be started independently after network.target.

from norns-image.

Shouldn't norns-crone have a dependency on norns-jack that ensures norns-crone only runs when norns-jack is running?
And the same for norns-maiden vs norns-matron?

from norns-image.

Sure, I kind of tried to reflect that in the nested structure of the list above. Inner items depend on parent items.

from norns-image.

Sure, I kind of tried to reflect that in the nested structure of the list above. Inner items depend on parent items.

Sorry, my reply wasn't very clear/explit. AFAIK Requires doesn't handle the case where the required unit fails.

From https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Requires=

Note that this dependency type does not imply that the other unit always has to be in active state when this unit is running

In our case I think we have a couple of services that can no longer function when their dependency dies.

from norns-image.

That would be awesome, but I cannot setup reliable monitoring for jackd at the moment (and its tools such as jack_wait also have false negatives), so I'd like to at least make sure it triggers a restart of crone when restarted.

from norns-image.

@artfwo I think this is all done at the moment, right?

from norns-image.

@simonvanderveldt yes, looks like it!

from norns-image.