Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rochester!cornell!uw-beaver!teknowledge-vaxc!mkhaw
From: mkhaw@teknowledge-vaxc.ARPA (Michael Khaw)
Newsgroups: comp.unix.questions,comp.unix.wizards
Subject: addendum - 4bsd ^Z handling and pipes
Message-ID: <13908@teknowledge-vaxc.ARPA>
Date: Sun, 21-Jun-87 01:28:56 EDT
Article-I.D.: teknowle.13908
Posted: Sun Jun 21 01:28:56 1987
Date-Received: Mon, 22-Jun-87 06:03:10 EDT
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 14
Keywords: there is a fork involved
Xref: mnetor comp.unix.questions:2899 comp.unix.wizards:2856

On further checking I found that Elm was forking, and the child elm was
doing an "_exit(foo(...))", where the foo() function was opening a pipe to
"more".  But I still would like to know what a ^Z handler needs to do so that 
a ^Z in more will not hang me.  It seems that currently the forked Elm gains
control, but it is trying to _exit().

Or is it that the parent fork needs to notice that wait() is returning
because of ^Z and do something with it?

Mike Khaw
-- 
internet:  mkhaw@teknowledge-vaxc.arpa
usenet:	   {hplabs|sun|ucbvax|decwrl|sri-unix}!mkhaw%teknowledge-vaxc.arpa
USnail:	   Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303