[comp.os.vms] ULTRIX pseudo-terminal driver bug?

carl@CITHEX.CALTECH.EDU (Carl J Lydick) (08/08/87)

Has anybody else seen either of the following problems under Ultrix 1.2 on
an all-DEC uVAX-II (or can anybody tell me if they're fixed in Ultrix 2.0)?
	1)  TELNET to the host machine, log in using the Bourne shell, nohup a
	    asynchronous subprocess, and log out.  The nohup'ed process
	    dies along with its parent.
	2)  Log in on a physical terminal line, send a long burst of characters
	    to the machine, and watch as it spews one of those characters
	    back at you until the system is rebooted (repeatedly halting the
	    processor and examining the PC shows the system to be in a tight
	    loop in the terminal driver).
The former problem shouldn't be related to the non-DEC hardware we've got
on the system, since we ARE using a DEQUNA; the latter I've only observed
on systems with EMULEX terminal multiplexer boards, since we don't have any
uVAXen with all-DEC terminal multiplexer boards.  Needless to say, if these
problems have been fixed in Ultrix 2.0, we've got some incentive to upgrade;
if not, my boss sees no reason not to stay with 1.2.