Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!udel!haven!uvaarpa!murdoch!kelvin.seas.Virginia.EDU!skg9h
From: skg9h@kelvin.seas.Virginia.EDU (Sharad Kumar Gandhi)
Newsgroups: comp.unix.aix
Subject: Re: how to crash AIX V3 on RISC SYSTEM 6000
Keywords: IBM crash aix hft graphics
Message-ID: <1991Apr15.195951.17449@murdoch.acc.Virginia.EDU>
Date: 15 Apr 91 19:59:51 GMT
References: <933@airgun.wg.waii.com>
Sender: usenet@murdoch.acc.Virginia.EDU
Organization: University of Virginia
Lines: 33

In article <933@airgun.wg.waii.com> markw@airgun.wg.waii.com (Mark Whetzel) writes:
>On any 6000 when a standard user is running AIXWINDOWS on the console
>they start X by issuing the xinit command.  While they are running
>if you perform a ps -u <userid> you will see a list of your processes
>that are owned by your account, this is fine and normal.  
>NOTE that there is a process, in addition to your shell and X server
>called 'kproc'.  I had a user that had a quick exit shell script that
>issued a 'kill -9 to all of their processes.  

i did same thing to come out from already hung up console.

>GUESS WHAT?  Killing the 'kproc' that is user owned will crash the
>entire system in a lockup, no LED fault codes, no system errors, just
>a complete lockup of the system.

	and it occured with my system too.
.
>I created a PMR 7E001 (problem managment request) with IBM on the problem
>about a non-privlidged user being able to crash the entire system.
>
>Their response was it was designed that way, and to change it will require
>a DCR (design change request).  I suggest that all users of this 'mis-feature'
>also request one of these, so we can fix this problem in the bud, before
>we all have problems with this.
>

	i am with you people for this good purpose.

>
>Mark Whetzel     My comments are my own, not my company's.


sharad (who love's himself)