From ad8302b50b20c57d5067c681a2bb1249ce2a28be Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Fri, 10 Apr 2026 12:47:59 +0000 Subject: Go a little easier on execline advocacy --- doc/overview.html | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'doc/overview.html') diff --git a/doc/overview.html b/doc/overview.html index b4f977a..164cffd 100644 --- a/doc/overview.html +++ b/doc/overview.html @@ -313,7 +313,7 @@ order. Very often, a run script can be reduced to a single command line - likely a long one, but still a single one. (That is the main reason why using the execline language -to write run scripts is recommended: execline makes it natural to handle +to write run scripts is a good idea: execline makes it natural to handle long command lines made of massive amounts of chain loading. This is by no means mandatory, though: a run script can be any executable file you want, provided that running it eventually results in a long-lived process with @@ -383,6 +383,9 @@ to check whether they're ready or not: s6-notifyoncheck. This is polling, which is bad, but unfortunately necessary for many daemons as of 2019. +
  • The s6-notify-fd-from-socket +program is the s6 way of supporting programs that use systemd's sd_notify() +notification mechanism.

    • -- cgit v1.3.1