leach@tolerant.com (Geoffrey Leach) (09/25/89)
I'm running AT&T UNIX release 3.2.1 on a generic 386AT. Occasionally, when I end a cu session (after the connection is terminated normally) the child process will hang in the <defunct> stage. (Modem is a TrailBlazer). Terminating the window in which the cu was run does not kill the zombie, and, of course, the parent hangs around as well. I have to reboot to get the port back. Any ideas?
max@lgc.UUCP (Max Heffler @ Landmark Graphics) (09/26/89)
In article <1989Sep24.171124.8124@tolerant.com>, leach@tolerant.com (Geoffrey Leach) writes: > Occasionally, when I end a cu session (after the connection > is terminated normally) the child process will hang in the > <defunct> stage. (Modem is a TrailBlazer). Terminating I have to terminate cu with ~. (Compaq 386/25 running ISC 386/ix 2.0.2) Have you tried this? -- Max Heffler uucp: ..!uunet!lgc!max Landmark Graphics Corp. phone: (713) 579-4751 333 Cypress Run, Suite 100 Houston, Texas 77094