From owner-freebsd-hackers Tue Aug 17 2:11:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relex.relex.ru (slip.relex.ru [195.98.69.100]) by hub.freebsd.org (Postfix) with ESMTP id 2F2A814BF6 for ; Tue, 17 Aug 1999 02:10:19 -0700 (PDT) (envelope-from alec@relex.relex.ru) Received: from alec.relex.ru (alec.relex.ru [195.98.69.163]) by relex.relex.ru (8.8.8/Relcom-2A) with SMTP id MAA15047 ;Tue, 17 Aug 1999 12:56:32 +0400 (MSD) Message-ID: <027401bee88f$2e503b90$a34562c3@alec.relex.ru> From: "Alec Kalinin" To: "Mark Newton" Cc: "Oleg Derevenetz" , Subject: Re: Probably bug with allocation memory in FreeBSD-3.2-RELEASE Date: Tue, 17 Aug 1999 13:02:06 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello ! > > 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. Yes. I try to modeling "out of swap" in FreeBSD-3.2-RELEASE. > > 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? I am sure, that setting limits in "/etc/login.conf" is not good decision. I try to explain. First of all, if i set limits more than swap space, one user can hung system. But, if i set limit equal half swap space, two different users can hung system. Than, i don't set limits for root process. And combinantion "squid + Netscape with java applet" from root may hung system. While 3.2-system can't simply kill this process like 2.2.8-system? I think, killing this process -- best solution. Good luck, Alec. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message