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
