Subject: Re: ptys are not always freed
To: Christoph Badura <firstname.lastname@example.org>
From: Todd Vierling <tv@NetBSD.ORG>
Date: 01/19/1998 15:45:03
On Mon, 19 Jan 1998, Christoph Badura wrote:
: >Do this only on a quiet system (so you'll be likely to be reallocated a tty
: >after you close it). Use screen 3.7.2 (or whatever version, really). Open
: >a screen, check which tty it is, and run either pine or emacs in it. Hit ^A
: >K (Ctrl-A then K). Open a screen again.
: Some versions of pine do not check for the the error code that 4.4BSD systems
: return in this case. Make sure your pine does handle the error correctly,
: if it gets reported.
Explain: "error code"? Which error code, and generated from what?
Is it correct to assume that a process should not be allowed to continue
holding on to a pty after its master side is closed, or can a program hold
on to it indefinitely if it ignores whatever error code you're referring to?
===== Todd Vierling (Personal email@example.com) =====
== "There's a myth that there is a scarcity of justice to go around, so
== that if we extend justice to 'those people,' it will somehow erode the
== quality of justice everyone else receives." -- Maria Price