On Wed, 8 Nov 2006, Dennis Clarke wrote:
> resources at hand. They do a very fine job of totally protecting me from
> such obscenities as :
>
> :(){ :|:& }; :
>
> When presented to the bash shell that seems to really upset the system. IT
> will completely crash a Red Hat Enterprise 4 server but my Solaris server
> here, left with stock bland /etc/system merely gets busy for a while. With
Heh. I should remember that one the next time some Linux weenie boasts of
how stable his Linux system is... :-)
> Possibly. I also wondered if the issue was that unzip is an IO bound
> process and not really limited to CPU and RAM. If these were IO bound
Could be...
> processes then I would think that there was some logical point at which the
> kernel would say "oops, I can't drive any more IO, so let's stop serviceing
> new processes".
I don't think that would happen; instead, you'd see the "b" kthr column
in vmstat increase.
> Precisely what I was thinking. Except that third column is "swapped out
> processes" and how does one pull them back from the brink of never never
> land? What ladel reaches into that bucket and when?
>
> I don't rightly know.
IIRC, everything will eventually get a chance to run, depending on what's
on the system at any one instant, and the priority and runnablity of the
processes. Even swpped out processes evntually get to run.
> This is the sort of theory that begs to be tested a bit eh ?
Sounds liek a fun idea. I once ran a fork bomb on my SB1000 for a few
minutes. As you say, Solaris didn't bat an eyelid, although the load
average was in the thousands.
--
Rich Teer, SCNA, SCSA, OpenSolaris CAB member
President,
Rite Online Inc.
Voice: +1 (250) 979-1638
URL: http://www.rite-group.com/rich
_______________________________________________
opensolaris-discuss mailing list
[email protected]
