bug-autoconf
[Top][All Lists]
Advanced

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

Re: On solaris, a SIGINT sent to a child process of Korn Shell kills the


From: Stefano Lattarini
Subject: Re: On solaris, a SIGINT sent to a child process of Korn Shell kills the shell itself
Date: Mon, 12 Sep 2011 22:03:09 +0200
User-agent: KMail/1.13.7 (Linux/2.6.30-2-686; KDE/4.6.5; i686; ; )

On Monday 12 September 2011, Paul Eggert wrote:
> On 09/12/11 11:17, Stefano Lattarini wrote:
> > this is due to the fact
> > that the Debian korn shell is apparently killing itself (yikes!) with the
> > same signal that killed the child process:
> 
> That's actually a fairly standard trick, one that I've seen in
> other programs.  The idea is that the invoking process should
> exit with the same status as the invoked process,
> even if the invoked process failed due to a signal.
>
I can see the point why some programs might want to do so, and I agree
that it can be useful in some selected circumstances.  But doing this
*be default* for a shell is IMHO wrong, and worse, only subtly wrong.

Maybe it would be acceptable on ksh part to enable the described
behaviour *if a special shell flag is activated*; but that should be
under complete control of the user.

> So my current guess is that that's why the Korn shell is
> doing what it's doing.
> 
> It's just that this trick doesn't work for the shell itself,
> at least, it doesn't always work in the presence of traps.
> 
So you basically agree with my opinion?

Thanks,
  Stefano


reply via email to

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