From 8f723b57193758cc7ecab296fe9eec69a8535db3 Mon Sep 17 00:00:00 2001
From: Laurent Bercot <ska-skaware@skarnet.org>
Date: Thu, 9 Apr 2026 02:40:03 +0000
Subject:  doc update for s6-notify-fd-from-socket

---
 doc/s6-notify-fd-from-socket.html | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/doc/s6-notify-fd-from-socket.html b/doc/s6-notify-fd-from-socket.html
index 2a8ea62..a6ab880 100644
--- a/doc/s6-notify-fd-from-socket.html
+++ b/doc/s6-notify-fd-from-socket.html
@@ -97,6 +97,14 @@ otherwise, leave it alone. </dd>
 <h2 id="notes"> Notes </h2>
 
 <ul>
+ <li> <tt>s6-notify-fd-from-socket</tt> only understands the <tt>READY=1</tt>
+line of the <tt>NOTIFY_SOCKET</tt> protocol. It will ignore any other line,
+and extensions will not be added. It will only work for readiness notification,
+and not for generic communication with the supervisor, fd transmission, or
+anything of the kind. There is a way to store file descriptors with s6:
+<a href="s6-fdholder-store.html">s6-fdholder-store</a>, which can be used in
+a run script, and is entirely independent from the readiness notification
+protocol. </li>
  <li> <tt>s6-notify-fd-from-socket</tt> is for daemons using the systemd
 protocol that you want to run under s6. If you want to do the opposite, i.e.
 run under systemd a daemon that uses the s6 notification protocol, use the
@@ -104,7 +112,5 @@ run under systemd a daemon that uses the s6 notification protocol, use the
 instead. </li>
 </ul>
 
-
-
 </body>
 </html>
-- 
cgit v1.3.1