diff options
| author | Laurent Bercot <ska-skaware@skarnet.org> | 2026-04-09 12:27:56 +0000 |
|---|---|---|
| committer | Laurent Bercot <ska-skaware@skarnet.org> | 2026-04-09 12:27:56 +0000 |
| commit | 48ada8ebe9cea0446e7c3c8490c99ac5eb9d87a0 (patch) | |
| tree | 999c8a2ff7c95972f3c5162309f8f9ab188b8202 | |
| parent | 8f723b57193758cc7ecab296fe9eec69a8535db3 (diff) | |
| download | s6-48ada8ebe9cea0446e7c3c8490c99ac5eb9d87a0.tar.gz | |
Doc update
| -rw-r--r-- | doc/s6-notify-socket-from-fd.html | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/s6-notify-socket-from-fd.html b/doc/s6-notify-socket-from-fd.html index ec2a57a..452cdb4 100644 --- a/doc/s6-notify-socket-from-fd.html +++ b/doc/s6-notify-socket-from-fd.html @@ -116,6 +116,13 @@ not using the systemd notification protocol, normally has no use for it. </dd> <h2 id="notes"> Notes </h2> <ul> + <li> <tt>s6-notify-socket-from-fd</tt> sends its notification as a subprocess +with a different pid from <em>prog</em>, so the unit file running the service +needs the <tt>NotifyAccess=all</tt> directive. </li> + <li> Despite <em>building</em> on every OS supported by s6, +<tt>s6-notify-socket-from-fd</tt> will only <em>work</em> on systems implementing +abstract sockets with autobind, which in practice means Linux 2.3.15 and later. +This is okay, because it is only useful to systemd users. </li> <li> This program was previously available on skarnet.org outside of any package, under the name <tt>sdnotify-wrapper</tt>. </li> <li> <tt>s6-notify-socket-from-fd</tt> is for s6-style daemons that you |