<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2017-08-22 16:23 GMT+02:00 Christoph Berg <span dir="ltr"><<a href="mailto:myon@debian.org" target="_blank">myon@debian.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I think you can simply use a drop-in config file:<br>
<br>
/etc/systemd/system/<wbr>postgresql@.service.d/type.<wbr>conf:<br>
[Service]<br>
Type=notify<br></blockquote><div><br></div><div>With this configuration, the systemctl command never returns.</div><div>To be sure I didn't made a mistake during my test, I have edited directly /lib/systemd/system/<span style="white-space:pre-wrap">postgresql@.service</span><br></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0)">systemctl stop postgresql</span><br></span></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0)">systemctl daemon-reload</span><br></span></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0)">systemctl start postgresql</span><br></span></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0)"><br></span></span></div><div>I have enabled full access to sd_notify with NotifyAccess=all in case of the signal comes from a subprocess, but it doesn't fix the behaviour.</div>
</div></div></div>