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

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



On 05.07.2010 01:02, Raphael Geissert wrote:
On Sunday 04 July 2010 00:04:20 Russ Allbery wrote:
Yeah, I was trying too hard to avoid a problem which doesn't really
exist.  Here's an updated patch.

diff --git a/policy.sgml b/policy.sgml
index bad28af..8b715d0 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -7427,7 +7427,18 @@ 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.
+	</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

Looks good now. Seconded.

As we have in "test" item, I think we should add ",if implemented as a
shell built-in," also for the kill command.

ciao
	cate



Reply to: