On Wed, 20 May 1998, Ionut Borcoman at musa wrote:
> Hi, > > If I do the followings in X: > > 1. start an xterm; > 2. in xterm give an su > 3. as root (under su) start mc > 4. close the xterm > > I end up with a 100% CPU usage, even when I do nothing. If I give top, I > discover that mc is still running and eating all the CPU power (say 98 <snip> This isn't the only thing that does this - try runing an xterm, opening elvis (vi - not vim), and then killing the xterm (using xkill, closing the window manager, or other method..) You will get a runaway vi taking up all your spare clock cycles. Not good. I think this is because these programs ignore hangup signals, and so when the shell dies, the hangup doesn't kill the process, even though it loses it's standard input - hence it 'running away' as it tries to read from an empty file stream. If anyone knows a simple way to prevent these problems - or if it has been classified as a bug - it'd be nice to know. Ta, Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]