[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#477240: Please clarify status of XSI extensions for kill and trap



Russ Allbery <rra@debian.org> writes:

> Good point.  Here's a new patch.  (This doesn't apply to trap because I
> don't think trap can work without having it implemented as a shell
> built-in.)

I've now merged this change for the next release.

> diff --git a/policy.sgml b/policy.sgml
> index 6c770fd..d694fd2 100644
> --- a/policy.sgml
> +++ b/policy.sgml
> @@ -7460,7 +7460,19 @@ fname () {
>  </example>
>  	      must be supported and must set the value of <tt>c</tt> to
>  	      <tt>delta</tt>.
> -            </item>
> +	    </item>
> +	    <item>The XSI extension to <prgn>kill</prgn> allowing <tt>kill
> +	      -<var>signal</var></tt>, where <var>signal</var> is either
> +	      the name of a signal or one of the numeric signals listed in
> +	      the XSI extension (0, 1, 2, 3, 6, 9, 14, and 15), must be
> +	      supported if <prgn>kill</prgn> is implemented as a shell
> +	      built-in.
> +	    </item>
> +	    <item>The XSI extension to <prgn>trap</prgn> allowing numeric
> +	      signals must be supported.  In addition to the signal
> +	      numbers listed in the extension, which are the same as for
> +	      <prgn>kill<prgn> above, 13 (SIGPIPE) must be allowed.
> +	    </item>
>  	  </list>
>  	  If a shell script requires non-SUSv3 features from the shell
>  	  interpreter other than those listed above, the appropriate shell

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>



Reply to: