On Mon, 19 Jan 2015 23:56, Jan Engelhardt <jengelh@...> wrote:
On Monday 2015-01-19 22:59, Yamaban wrote:
But then we should make sure that the actual apparmor.service file contains the needed "ExecReload=" line else it's pre-defined as SIGHUP to the process pid
You are wrong. There is no such predefinition.
One more cause to define it.
Absolutely not. Your suggestion does more harm than without.
Some programs may not handle SIGHUP, and then exit if they get it anyway. So you just turned "reload" into "stop", more or less. Not good.
Other programs, like cupsd-1.5.4, set to ignore SIGHUP. So you just turned "reload" from an informative "sorry, cups.service does not support it" error into a succeeding silent no-op. Not good.
So next time, think things through first.
Please do not misconstruct such from my reply, the reply only was minted for 'apparmor', and 'apparmor' alone. And I can count more than 14 'services' where SIGHUP for 'reload' would be wrong, just from Factory repo. And a signal via kill is most NOT the ideal way for a reload, as no responce code is given from the main process. If 'service' programs would be nice, they them self would implement parameters like 'stop' 'reload-config' 'reopen-logfile' and such, while detecting the 'master' process themself. But there is no such framework, sadly. - Yamaban -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org