diff options
Diffstat (limited to 'doc')
-rw-r--r-- | doc/index.html | 4 | ||||
-rw-r--r-- | doc/upgrade.html | 11 | ||||
-rw-r--r-- | doc/wait.html | 20 |
3 files changed, 29 insertions, 6 deletions
diff --git a/doc/index.html b/doc/index.html index 9a01f17..69fa015 100644 --- a/doc/index.html +++ b/doc/index.html @@ -51,7 +51,7 @@ shell's syntax, and has no security issues. <li> A POSIX-compliant system with a standard C development environment </li> <li> GNU make, version 3.81 or later. </li> <li> <a href="//skarnet.org/software/skalibs/">skalibs</a> version -2.11.2.0 or later. It's a build-time requirement. It's also a run-time +2.12.0.0 or later. It's a build-time requirement. It's also a run-time requirement if you link against the shared version of the skalibs library. </li> </ul> @@ -77,7 +77,7 @@ want nsswitch-like functionality: <h3> Download </h3> <ul> - <li> The current released version of execline is <a href="execline-2.8.3.0.tar.gz">2.8.3.0</a>. </li> + <li> The current released version of execline is <a href="execline-2.9.0.0.tar.gz">2.9.0.0</a>. </li> <li> Alternatively, you can checkout a copy of the <a href="//git.skarnet.org/cgi-bin/cgit.cgi/execline/">execline git repository</a>: diff --git a/doc/upgrade.html b/doc/upgrade.html index 534ad57..705f03a 100644 --- a/doc/upgrade.html +++ b/doc/upgrade.html @@ -18,6 +18,17 @@ <h1> What has changed in execline </h1> +<h2> in 2.9.0.0 </h2> + +<ul> + <li> <a href="//skarnet.org/software/skalibs/">skalibs</a> +dependency bumped to 2.12.0.0. </li> + <li> New options to <a href="wait.html">wait</a>: <tt>-o</tt> +to wait for one of the listed processes, and <tt>-a</tt> to get the +default behaviour. </li> + <li> <a href="wait.html">wait</a> now exits 99 on timeout. </li> +</ul> + <h2> in 2.8.3.0 </h2> <ul> diff --git a/doc/wait.html b/doc/wait.html index a092859..a66cefc 100644 --- a/doc/wait.html +++ b/doc/wait.html @@ -29,7 +29,7 @@ </p> <pre> - wait [ -I | -i ] [ -r | -t <em>timeout</em> ] { [ <em>pids...</em> ] } <em>prog...</em> + wait [ -I | -i ] [ -a | -o ] [ -r | -t <em>timeout</em> ] { [ <em>pids...</em> ] } <em>prog...</em> </pre> <ul> @@ -57,7 +57,18 @@ milliseconds, they will not be reaped. </li> waiting for children to die, it will still exec into <em>prog...</em>. This is the default. </li> <li> <tt>-i</tt> : strict. If <tt>wait</tt> times out, it -will print an error message and exit 1. </li> +will print an error message and exit 99. </li> + <li> <tt>-o</tt> : wait for <em>one</em> of the listed +<em>pids</em> — exec into <em>prog</em> as soon as one of the +listed children dies. (If no pid is listed, wait for one child to die.) +The <tt>!</tt> environment variable will be set to the +pid that died, and the <tt>?</tt> environment variable will contain an +<a href="exitcodes.html">approximation</a> of its exit code. If no +listed child has died before <tt>wait</tt> has to exec (either because +it timed out or it has no suitable children left), the <tt>?</tt> and +<tt>!</tt> environment variables are unset. </li> +<li> <tt>-a</tt> : wait for <em>all</em> of the listed <em>pids</em>. +Do not touch the <tt>!</tt> or <tt>?</tt> variables. This is the default. </li> </ul> <h2> Notes </h2> @@ -65,8 +76,9 @@ will print an error message and exit 1. </li> <ul> <li> For <a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/wait.html">POSIX compatibility</a>, <tt>wait</tt> also works when it cannot find a block. -In that case, all its command line is interpreted as <em>pids...</em> -arguments and it does not execute into a program. Instead, it exits +In that case, all the options are still supported and have the same +effect, but the rest of the command line is interpreted as <em>pids...</em> +arguments and <tt>wait</tt> does not execute into a program; instead, it exits with a conforming exit code. </li> </ul> |