rang@cpsin3.cps.msu.edu (Anton Rang) (12/06/88)
I had some line noise while dialing in one day, and it wound up with me typing the line "kill | %1". The shell responded with: kill | Stopped (tty output) I did an 'fg' to bring the kill into the foreground (so I could use ^C to kill it, I was lazy) and wound up stuck. The "kill" subjob never woke up. This happens both under SunOS 3.4 and Ultrix 2.2, so I suspect it's a problem in 4.2 BSD. Hmm...I just tried it under SunOS 4.0. The first time, it came back with kill: kill | Too few arguments. I typed it in again, and got: kill | Stopped (tty output) A "jobs" command gives: [1] + Stopped (tty output) kill | but "kill %1" gives "No such process." Typing in "kill | %1" one more time results in "kill |" and a hang. Is this a known problem, and if so, is a fix available? +---------------------------+------------------------+----------------------+ | Anton Rang (grad student) | "VMS Forever!" | "Do worry...be SAD!" | | Michigan State University | rang@cpswh.cps.msu.edu | | +---------------------------+------------------------+----------------------+