From owner-freebsd-bugs  Mon Jul 28 00:20:09 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id AAA15204
          for bugs-outgoing; Mon, 28 Jul 1997 00:20:09 -0700 (PDT)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id AAA15172;
          Mon, 28 Jul 1997 00:20:02 -0700 (PDT)
Date: Mon, 28 Jul 1997 00:20:02 -0700 (PDT)
Message-Id: <199707280720.AAA15172@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: Bruce Evans <bde@zeta.org.au>
Subject: Re: kern/4113: Re: Processes shouldn't get SIGIO when the tty is set to CLOCAL
Reply-To: Bruce Evans <bde@zeta.org.au>
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/4113; it has been noted by GNATS.

From: Bruce Evans <bde@zeta.org.au>
To: FreeBSD-gnats-submit@FreeBSD.ORG, leres@ee.lbl.gov
Cc:  Subject: Re: kern/4113: Re: Processes shouldn't get SIGIO when the tty is set to CLOCAL
Date: Mon, 28 Jul 1997 17:14:12 +1000

 >Subject: kern/4113: Re: Processes shouldn't get SIGIO when the tty is set to CLOCAL
 
 I'm not sure what the correct behaviour is here.  One could argue
 that SIGIO should never be delivered for carrier rises, since carrier
 transitions aren't i/o.  OTOH, it may be useful to deliver a SIGIO for
 all state transitions in the driver, in case the application cares.
 This would be particularly useful for monitoring the carrier state in
 CLOCAL mode :-).  Applications that want to monitor the carrier state
 usually use alarms, but this gives a high latency.
 
 Bruce