On 07/09/2010 02:05 AM, Johannes Sixt wrote: > From: Johannes Sixt <j6t@xxxxxxxx> > > ksh is known to report $? of programs that terminated by a signal as > 256 + signal number instead of 128 + signal number like other POSIX > compliant shells. (ksh's behavior is still POSIX compliant in this regard.) This may only be true for Ksh93. The Ksh88 man page says that the exit status is 128+signum. The Public domain Korn shell, and ksh on IRIX 6.5, Solaris 7, 9, and 10 all exit with the standard behavior of 128+signum. So, it may be appropriate to change the commit message and comment in t0005 to reflect this fact. -Brandon > t/t0005-signals.sh | 1 + > 1 files changed, 1 insertions(+), 0 deletions(-) > > diff --git a/t/t0005-signals.sh b/t/t0005-signals.sh > index 09f855a..93e58c0 100755 > --- a/t/t0005-signals.sh > +++ b/t/t0005-signals.sh > @@ -13,6 +13,7 @@ test_expect_success 'sigchain works' ' > test-sigchain >actual > case "$?" in > 143) true ;; # POSIX w/ SIGTERM=15 > + 271) true ;; # ksh w/ SIGTERM=15 > 3) true ;; # Windows > *) false ;; > esac && -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html