From owner-freebsd-hackers  Fri Nov 15 10:52:44 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA07906
          for hackers-outgoing; Fri, 15 Nov 1996 10:52:44 -0800 (PST)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA07895
          for <hackers@FreeBSD.org>; Fri, 15 Nov 1996 10:52:34 -0800 (PST)
Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id KAA18955; Fri, 15 Nov 1996 10:50:52 -0800 (PST)
Message-Id: <199611151850.KAA18955@austin.polstra.com>
To: Bruce Evans <bde@zeta.org.au>
cc: jgreco@brasil.moneng.mei.com, karl@Mcs.Net, hackers@FreeBSD.org,
        scrappy@ki.net
Subject: Re: Sockets question... 
In-reply-to: Your message of "Sat, 16 Nov 1996 05:35:16 +1100."
             <199611151835.FAA22344@godzilla.zeta.org.au> 
References: <199611151835.FAA22344@godzilla.zeta.org.au> 
Date: Fri, 15 Nov 1996 10:50:52 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> >Can't.  Any signal on that process is a SERIOUS error; its a DBMS!  We have
> >a generic "oh shit" trap for all signals set; it does not go off.
> 
> Don't do that for SIGIO.  Anyone can send SIGIO to any process.

Really?!  Gads, KILL(2) doesn't say anything about that.

I believe you, but isn't that a bug?  Is there some useful purpose
served by allowing it?

John