Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!hal!ncoast!allbery
From: allbery@ncoast.UUCP (Brandon S. Allbery)
Newsgroups: comp.unix.wizards
Subject: Re: How can I read keyboard without stopping
Message-ID: <12302@ncoast.UUCP>
Date: 28 Aug 88 21:07:06 GMT
References: <813@ms3.UUCP> <1246@mcgill-vision.UUCP> <1202@tjalk.cs.vu.nl> <373@marob.MASA.COM>
Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery)
Followup-To: comp.unix.wizards
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 24

As quoted from <373@marob.MASA.COM> by daveh@marob.MASA.COM (Dave Hammond):
+---------------
| In article <1202@tjalk.cs.vu.nl> maart@cs.vu.nl () writes:
| >In article <1246@mcgill-vision.UUCP> mouse@mcgill-vision.UUCP (der Mouse) writes:
| >\		- generally, non-blocking mode *must* be turned off or
| >\		  the shell will die - so you must trap SIGBUS,
| >\		  SIGSEGV, SIGINT, etc.
| >Are you saying that the shell will die if a CHILD sets the non-blocking mode?
| >I guess your operating system isn't Unix.
| 
| Mine is (Unix), and yes, the shell dies if a child dies with the terminal in
| non-blocking mode -- every time.  At least sh and ksh do; I don't know 'bout csh
| but I suspect the same is true.
+---------------

Keep in mind that dup()'ed file descriptors and file descriptors inherited
across a fork() share a file table entry -- and it is the file table entry
that holds the O_NDELAY (FNDELAY on BSD) flag.  So yes, if a child changes
the no-delay status the parent sees it also.

++Brandon
-- 
Brandon S. Allbery, uunet!marque!ncoast!allbery			DELPHI: ALLBERY
	    For comp.sources.misc send mail to ncoast!sources-misc