Re: Help : kill -9 pid does not work!!!

New Message Reply Date view Thread view Subject view Author view

ken sartor (sartor++at++visidyne.com)
Wed, 24 Jun 1998 13:20:39 -0500


At 12:48 PM 6/24/98 -0400, Jean Daigle wrote:
>Hi,
>
>On Jun 24, 1:13pm, Dr Colin Bridgewater wrote:
>...
>} Hi Ren
>}
>} Ren-Jye Yu wrote:
>} > Thanks for you reply. You are right. My code spawn up to 3 process.
>} > I can kill two of them. Always the one that has the smallest pid
>} > number that i could kill. Any suggestions?
>}
>} Are you saying that you can't kill off the initial (spawning) process
>} using killall or kill, even as root ? That doesn't sound right to me.
>...
>}-- End of excerpt from Dr Colin Bridgewater
>
>Whether or not it sounds right, it was indeed the case for us
>on Onyx RE^2 with Performer 2.0.4 until we installed patchSG0002739.
>
>Occasionally, wayward graphics processes would hang, preventing
>use of the graphics console and inhibiting the launch of any
>more processes accessing the display.
>
>These processes were unkillable by root (well, the APP process
>could be killed, and what appeared to be the DRAW process would
>become a zombie, and never be cleared up by init the way the man
>page says should happen periodically). Stopgfx/startgfx was
>ineffective. The only workaround to regain access to graphics
>was to reboot the machine.
>
>Obviously, user processes should not have this disruptive
>power on a multi-user machine. However, it was most definitely
>the case.

I also saw this behaviour on my Onyx RE2. It vanished
when i upgraded from Performer 2.04 / Performer 2.1 to
Performer 2.2. It happened at unpredictable times and
neither the vulcan death grip, killing the x display
manager via kill, or using stopgfx and startgfx had any
effect whatsoever. The only solution i could find was
to reboot...

ken
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
            Submissions: info-performer++at++sgi.com
        Admin. requests: info-performer-request++at++sgi.com


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:57:35 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.