unexpected service restart on initctl reload, notify-related?

[az143]

unexpected service restart on initctl reload, notify-related?

[az143]

On Sun, 29 Oct 2023 17:15:14 -0700, Joachim Wiberg writes:

Closed #382 as completed via 84adec4.

wow, that was super-quick - thank you! regards, az

…

-- Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + https://snafu.priv.at/ "Unterschätze nie die Macht dummer Leute, die einer Meinung sind." -- Kurt Tucholsky

[troglobit]

Hmm, service/B/ready shouldn't be cleared on reload(flux). I'll have to get back to you on that one.

The reason for C and D not being restarted is that you have declared them as supporting SIGHUP. The special character ! at the beginning of <> is a declaration a service does not support SIGHUP and will thus be stop/started instead, which I assume is what you expected here.

[az143]

On Sun, 29 Oct 2023 10:15:09 -0700, Joachim Wiberg writes:

Hmm, service/B/ready shouldn't be cleared on reload(flux). I'll have to get back to you on that one.

anything that i can do to help with this?

…

-- Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + https://snafu.priv.at/ IBM - "Internally Blackened Machines" -- Bob Vaughan about PSU failures

[troglobit]

anything that i can do to help with this?

I'm using a stripped down version of your test to reproduce. Pretty sure I've located the culprit, but will take a while to close it due to research into why we have this behavior and also $DAYJOB.