From owner-freebsd-bugs  Mon Jul 28 03:40:05 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id DAA22869
          for bugs-outgoing; Mon, 28 Jul 1997 03:40:05 -0700 (PDT)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id DAA22829;
          Mon, 28 Jul 1997 03:40:01 -0700 (PDT)
Date: Mon, 28 Jul 1997 03:40:01 -0700 (PDT)
Message-Id: <199707281040.DAA22829@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: Craig Leres <leres@ee.lbl.gov>
Subject: Re: kern/4113: Re: Processes shouldn't get SIGIO when the tty is set to
Reply-To: Craig Leres <leres@ee.lbl.gov>
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: Craig Leres <leres@ee.lbl.gov>
To: Bruce Evans <bde@zeta.org.au>
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/4113: Re: Processes shouldn't get SIGIO when the tty is set to
Date: Mon, 28 Jul 1997 03:30:43 PDT

 > >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.
 
 The truth is, I think they're crazy for using SIGIO in xntpd... But
 since it's not my furball my main interest is in making xntpd run as
 well on FreeBSD as it does on other Unix systems. (And if an app wants
 to monitor the carrier state while in CLOCAL mode, it will only work
 under FreeBSD.)
 
 		Craig