From facc1fb44783a1c66070403ae70343b1ab9858ee Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Thu, 9 Apr 2026 13:47:44 +0000 Subject: Correct the doc update >.> --- doc/s6-notify-socket-from-fd.html | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) (limited to 'doc/s6-notify-socket-from-fd.html') diff --git a/doc/s6-notify-socket-from-fd.html b/doc/s6-notify-socket-from-fd.html index 452cdb4..a1f68d2 100644 --- a/doc/s6-notify-socket-from-fd.html +++ b/doc/s6-notify-socket-from-fd.html @@ -21,7 +21,7 @@

s6-notify-socket-from-fd is different from other chainloading -tools in s6, in as it's not meant to be used in s6 run scripts. Instead, +tools in s6: it's not meant to be used in s6 run scripts. Instead, it's meant to be used when you're not using s6, but another service manager that does not support the s6 readiness notification protocol, @@ -119,12 +119,8 @@ not using the systemd notification protocol, normally has no use for it.

  • s6-notify-socket-from-fd sends its notification as a subprocess with a different pid from prog, so the unit file running the service needs the NotifyAccess=all directive.
    • -
  • Despite building on every OS supported by s6, -s6-notify-socket-from-fd will only work 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.
    • -
  • This program was previously available on skarnet.org outside of any -package, under the name sdnotify-wrapper.
    • +
  • An early version of this program was previously available on skarnet.org, +unpackaged, under the name sdnotify-wrapper.
  • s6-notify-socket-from-fd is for s6-style daemons that you want to run under systemd. If you want to do the opposite, i.e. run under s6 a daemon that uses the systemd protocol, use the -- cgit v1.3.1