Dan Sugalski  [EMAIL PROTECTED] writes:
> At 07:20 AM 3/10/00 -0500, Charles Lane wrote:
> >It's worse for a child writing to a parent that has closed its input;
> >the child has no way to tell that the parent has taken that action,
> >and (in the parent) we don't have a way to $CANCEL or otherwise have
> >the child's $QIO return an error.

> Maybe we should nuke the child when we close the filehandle open to it?

I don't think so, it might not be done doing whatever it does.  The
example 'test_contend.pl' that I posted a couple of days ago is like
that...the input to to child is just a "go!" to tell it to start
spewing output.

We do wait for child completion when we close, that behavior is unchanged.
If you want to kill the child first, do a "kill $pid" before closing the
filehandle, but I don't think we should make that the default.
--
 Drexel University       \V                     --Chuck Lane
----------------->--------*------------<[EMAIL PROTECTED]
     (215) 895-1545      / \  Particle Physics  [EMAIL PROTECTED]
FAX: (215) 895-5934        /~~~~~~~~~~~         [EMAIL PROTECTED]

Reply via email to