[systemd-devel] Question regarding the NotifyAccess parameter

Zbigniew Jędrzejewski-Szmek zbyszek at in.waw.pl
Tue Nov 26 06:32:28 PST 2013


On Thu, Nov 21, 2013 at 08:56:25PM +0530, salil GK wrote:
> Hello
> 
>    I have a service in shell script in which I am sending notification to
> systemd using `systemd-notify WATCHDOG=1` command. What happens is -
> systemd-notify will be a child process and in the systemd notification will
> not be honoured if NotifyAccess is set to main. Is there any work around
> for this.
Use NotifyAccess=all?

>    One more issue I observed is - if I specify Restart=on-failure, if
> watchdog timer expire, it restart the service. But I can see that it create
> two processes rather than restarting the process. But if I do systemctl
> restart Myservice , it kills the previous instance of service and start a
> new service. Any pointers on why it happens so.
That would be a significant bug! Can you post a short example which shows
the bug?

Zbyszek


More information about the systemd-devel mailing list