From owner-freebsd-stable Sat May 5 15:51: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw.plaintalk.bellevue.wa.us [206.129.5.130]) by hub.freebsd.org (Postfix) with ESMTP id 5A00937B422 for ; Sat, 5 May 2001 15:51:01 -0700 (PDT) (envelope-from dennisg@software-munitions.com) Received: from localhost (dennisg@localhost) by btw.plaintalk.bellevue.wa.us (8.11.3/8.11.3) with ESMTP id f45Moi001111; Sat, 5 May 2001 15:50:44 -0700 (PDT) (envelope-from dennisg@software-munitions.com) Date: Sat, 5 May 2001 15:50:44 -0700 (PDT) From: Dennis Glatting X-X-Sender: To: Alfred Perlstein Cc: Dennis Glatting , Subject: Re: pgm to kill 4.3 via vm In-Reply-To: <20010505154315.G18676@fw.wintelcom.net> Message-ID: <20010505154808.Y1076-100000@btw.plaintalk.bellevue.wa.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 5 May 2001, Alfred Perlstein wrote: > * Dennis Glatting [010505 14:38] wrote: > > > > I wrote a trivial program to fill vm and found I can reliably freeze my > > system. It may not work on the first attempt, but certainly within three. > > My command line is: > > > > a.out&;a.out&;a.out&;a.out&;a.out& > > > > The goal of my program is simply to see how the system behaves under > > memory exhaustion which, as it turns out on two similar systems, the > > systems freeze. Specifically, I can switch between consoles but the login > > prompts do not respond and the system does not respond on the network. > > > > I am running 4.3 on a dual processor system. > > > > Below are some things. First, the program. Second, dmesg. Finally, my > > /etc/rc.config. > > > > LOL > > There's no reason to cc two lists. > > You've obviously not bothered to read manpages on setting up system > limits, please do so. > Why is it expected behaviour for a system to freeze, thus requiring a power cycle, regardless of system limit settings? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message