Am 09.04.22 um 10:00 schrieb Yolo von BNANA:
------- Original Message -------
On Friday, April 8th, 2022 at 13:49, Lennart Poettering <lennart@xxxxxxxxxxxxxx> wrote:
This could be done better. Plugging in just a "kill" here, means the
reload is async. i.e. "systemctl reload" will basically return
immediately without the reload being complete, thus subsequent
commands can't rely the new config is already in place.
It's typically nicer to invoke some synchronous command from
ExecReload=.
Can you please explain this in more Detail?
What does this mean: " "systemctl reload" will basically return
immediately without the reload being complete"?
And what is an Example for an synchronous command for ExecReload=
It seems that killing with USR1|USR2|HUP is commonly used:
$ grep -R ExecReload /usr/lib/systemd/|grep -v kill|wc -l
19
$ grep -R ExecReload /usr/lib/systemd/|grep kill|wc -l
27
Following statement is from
$ man 8 smbd
Instead of sending a SIGHUP signal, a request to reload
configuration file may be sent using smbcontrol(1) program.
albeit beforehand they suggest SIGHUP.
--
Leon
