rhare@carina.unm.edu (11/12/89)
The other day I was testing lots of output to a DECstation 3100 from the network. I had 4 windows open each doing lots of output. (ie. ls -R from /) I decided that I didn't really want to stop each process (laziness at its finest) and simply did a quit from the dxsession window. Next a user logs into the DECstation. They open a window and all the output from my process suddenly appears in their window. I was unable to break out of the program however ps reported my process still running and attached to their pty. Is this a problem in the pty driver? This is the second time I have seen this happen. Has anyone else had this problem? Thanks, Robert Hare rhare@ariel.unm.edu
swatt@cup.portal.com (Steven Edward Watt) (11/13/89)
rhare@ariel.unm.edu write: >The other day I was testing lots of output to a DECstation 3100 from the >network. I had 4 windows open each doing lots of output. (ie. ls -R from /) >I decided that I didn't really want to stop each process (laziness at its >finest) and simply did a quit from the dxsession window. Next a user logs >into the DECstation. They open a window and all the output from my process >suddenly appears in their window. I was unable to break out of the program >however ps reported my process still running and attached to their pty. Is >this a problem in the pty driver? This is the second time I have seen this >happen. Has anyone else had this problem? Yes, several times... If you start a background process that is nohup'ed, and it writes sporadic output, the pty will recieve that output until the program dies, as far as I can tell... An occasionally useful feature, I might add. (To kill the dxterm that's on that pty and start an xterm with a more useful scroll bar.) >Thanks, You're welcome! >Robert Hare >rhare@ariel.unm.edu Steve Watt swatt@cup.portal.com ...!ucbvax!sun!cup.portal.com!swatt