m4-commit
[Top][All Lists]
Advanced

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

Changes to m4/doc/m4.texinfo,v [branch-1_4]


From: Eric Blake
Subject: Changes to m4/doc/m4.texinfo,v [branch-1_4]
Date: Mon, 05 Feb 2007 13:25:07 +0000

CVSROOT:        /sources/m4
Module name:    m4
Branch:         branch-1_4
Changes by:     Eric Blake <ericb>      07/02/05 13:25:06

Index: doc/m4.texinfo
===================================================================
RCS file: /sources/m4/m4/doc/m4.texinfo,v
retrieving revision 1.1.1.1.2.112
retrieving revision 1.1.1.1.2.113
diff -u -b -r1.1.1.1.2.112 -r1.1.1.1.2.113
--- doc/m4.texinfo      3 Feb 2007 23:11:24 -0000       1.1.1.1.2.112
+++ doc/m4.texinfo      5 Feb 2007 13:25:06 -0000       1.1.1.1.2.113
@@ -5152,17 +5152,19 @@
 @comment exits normally rather than letting the signal terminate it).
 @comment Also, TERM is flaky, as it can also kill the running m4 on
 @comment systems where /bin/sh does not create its own process group.
address@hidden That leaves KILL and PIPE as the two signals tested.
address@hidden And PIPE is unreliable, since people tend to run with it
address@hidden ignored, with m4 inheriting that choice.  That leaves KILL as
address@hidden the only signal we can reliably test.
 @example
 dnl This test assumes kill is a shell builtin, and that signals are
 dnl recognizable.
 ifdef(`__unix__', ,
       `errprint(` skipping: syscmd does not have unix semantics
 ')m4exit(`77')')dnl
-syscmd(`kill -13 $$')
+syscmd(`kill -9 $$')
 @result{}
 sysval
address@hidden
address@hidden
 esyscmd(`kill -9 $$')
 @result{}
 sysval




reply via email to

[Prev in Thread] Current Thread [Next in Thread]