murthy@svax.UUCP (02/13/87)
I posted something previously about problems with X on : IBM RTs running ACIS (one of the first releases to support X) SUN-2s running OS 3.0 SUN-3s running OS 3.2 uVaxen running 4.3bsd now, a Gould 9080 running UTX/32 rel 1.3 On all these machines, rsh-ed xterms will hang if the running process inside exits without being killed by the xterm. Basically, all you do is rsh the xterm into existence, with or without the -ls option, and when you hit control-D to the C-shell, or exit, or logout, at LEAST 25% of the time on the Gould all the time on the uVaxen and RTs 10% of the time on the SUNs the xterm will die ungracefully, leaving the window upen, the socket still connected, and the pty on the remote machine still operational. This bug has been observed by only one other person on the net, and his fix didn't seem to solve the problem except on the SUNs (it was to do a setpgrp(0,0) if the xterm was running thru rsh). So, if any of you out there run the same exact configuration as me, and have X.V10R4, and xterm works like a charm, even rsh-ed, could you let me know? The real clincher is to get 4 or 5 xterms stacked up, and then kill then really fast with control-D to the c-shells inside. This almost always gets at least one hung xterm. Thanks in Advance, -- --chet-- In Real Life: Chet Murthy ARPA: murthy@svax.cs.cornell.edu SnailMail: Chet Murthy Gaslight Village Apts 21-B Uptown Road Ithaca, NY 14850 MaBellNet: (607)-257-5709