[comp.windows.x] bug in xterm assigning pty

phil@ux1.cso.uiuc.edu (09/27/90)

I have found the following bug in xterm, and wonder if anyone else has seen it.
I don't have an opportunity to fix it here since I don't do that here.

The bug is that xterm will choose a pty/tty pair without checking to see if
the tty (slave) side is full usable.  If some other process leaves its tty
open, runs in the background, and its shell logs out (with the subsequent
release of its pty) that pair appears to be reusable.  The script and rlogind
programs have explicit tests to see if the tty side is usable after opening
the pty side, and if not, abandons that pair and goes on to another.  It seems
that xterm lacks this test.

--Phil Howard, KA9WGN-- | Individual CHOICE is fundamental to a free society
<phil@ux1.cso.uiuc.edu> | no matter what the particular issue is all about.