From owner-freebsd-hackers Tue Aug 17 1:30:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id DD97915630 for ; Tue, 17 Aug 1999 01:30:25 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id RAA70438; Tue, 17 Aug 1999 17:56:56 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199908170826.RAA70438@gizmo.internode.com.au> Subject: Re: Probably bug with allocation memory in FreeBSD-3.2-RELEASE To: alec@relex.ru (Alec Kalinin) Date: Tue, 17 Aug 1999 17:56:55 +0930 (CST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <01b001bee885$cca7b570$a34562c3@alec.relex.ru> from "Alec Kalinin" at Aug 17, 99 11:54:57 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alec Kalinin wrote: > I think, mentioned below program probably show the bug in virtual memory > subsystem in FreeBSD-3.2-RELEASE. After running this program, FreeBSD comes > into "out of swap" state, then hungs. Well, yeah, that's becuase you're running it out of swap by trying to allocate a gigabyte of memory. > Why i think this is bug? Because any user can hung FreeBSD, settings in > /etc/login.conf can't help. Are you sure about that? Setting datasize limits will prevent malloc() from doing what you're trying to make it do. Are you sure you're setting your login.conf settings properly? - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message