Subject: Re: bin/6213: /bin/sh mishandles trapped signals during "read"
To: None <netbsd-bugs@netbsd.org>
From: Urban Boquist <boquist@cs.chalmers.se>
List: netbsd-bugs
Date: 09/30/1998 18:28:29
>>>>> Christoph Badura writes:

>> If you "trap" SIGTERM and then execute the sh builtin "read", the
>> shell will not react to SIGTERM until the "read" is done (you have
>> to press RETURN).

Christoph> And what makes you think this is a bug?

The fact that it worked as I thought it should in the other "Bourne
shell alikes" that I happened to have around: NetBSD /bin/ksh, NetBSD
bash, and Solaris /bin/sh. Of course, neither of these is a "real
Bourne shell".

Christoph> I mean, a real Bourne shell behaves the same with you example.

I think that is a mostly irrelevant question, since NetBSD's /bin/sh
is not a real Bourne shell either. In fact, the manual page does not
even mention the word "Bourne"! It  talks about Posix, and mentions
Korn shell and Bash.

Regards,

        -- Urban

P.S. According to a FreeBSD person the problem is fixed in FreeBSD-3.0.