1️⃣9️⃣ Here's the 19th post highlighting key new features of the recently released v259 release of systemd. #systemd259 #systemd

Each systemd service has various ExecXYZ= stanzas that control what command to execute on which operation. Most importantly, there's of course ExecStart= which configures the command to run for actually starting the service. Then there's ExecStartPre=, ExecStartPost=, ExecReload=, ExecStop=, ExecStopPost=.

And with systemd v259 there's one more knob like this:

ExecReloadPost= defines a command line to execute after ExecReload= succeeded. It can issue additional commands after a service completed reloading its configuration. In case of Type=notify-reload services (which btw is the recommend choice these days) this means the READY=1 message from the service's main process is the the trigger for going for ExecReloadPost=. Or in other words: if you need to run some command whenever a service is known to have the most recent configuration…

…fully in effect, this is where you can hook it in.

It's hence a bit like ExecStartPost=, which is similarly called once a service is fully operational with its *initial* configuration, except that for ExecReloadPost= it's about *later* versions of the configuration.

@pid_eins TIL "Type=notify-reload service". So you have a service with that type that you trigger and this triggers another service to restart?!