Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!hp4nl!star.cs.vu.nl!maart
From: maart@cs.vu.nl (Maarten Litmaath)
Newsgroups: comp.unix.questions
Subject: Re: PTY's
Message-ID: <7177@star.cs.vu.nl>
Date: 26 Jul 90 00:24:46 GMT
References: <*%2$X6-@rpi.edu> <7170@star.cs.vu.nl> <5756:Jul2520:37:5490@kramden.acf.nyu.edu>
Sender: news@cs.vu.nl
Reply-To: maart@cs.vu.nl (Maarten Litmaath)
Organization: VU Dept. of Computer Science, Amsterdam, The Netherlands
Lines: 24

In article <5756:Jul2520:37:5490@kramden.acf.nyu.edu>,
	brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
)...
)Convention dictates that the pty is used only until the child exits; [...]

Hmm, this seems normal behavior indeed, but in general I'd like _any_
pipeline using `pty' or `mtty' to work just like it would without using
the pseudo tty utility...  [Note: both `pty' and `mtty' close the pty if
the child exits.]

)...
)The master *can* handle the I/O while waiting for a SIGCHLD; it just
)mustn't die within the SIGCHLD handler.

That was not my problem; I was thinking of output getting lost without
proper indication how much has been written, but this can be fixed indeed
using restartable system calls.

)Look at the pty code [...]

I will.
--
 "and with a sudden plop it lands on usenet.  what is it? omigosh, it must[...]
   be a new user! quick kill it before it multiplies!"      (Loren J. Miller)