From owner-freebsd-bugs@FreeBSD.ORG Fri Jun 13 02:30:13 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F7C237B401 for ; Fri, 13 Jun 2003 02:30:13 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECF4743FB1 for ; Fri, 13 Jun 2003 02:30:12 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h5D9UCUp034798 for ; Fri, 13 Jun 2003 02:30:12 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h5D9UChf034797; Fri, 13 Jun 2003 02:30:12 -0700 (PDT) Date: Fri, 13 Jun 2003 02:30:12 -0700 (PDT) Message-Id: <200306130930.h5D9UChf034797@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: David Schultz Subject: Re: kern/53257: malloc() never returns 0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Schultz List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jun 2003 09:30:13 -0000 The following reply was made to PR kern/53257; it has been noted by GNATS. From: David Schultz To: Tony Gottfridsson Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/53257: malloc() never returns 0 Date: Fri, 13 Jun 2003 02:27:41 -0700 On Thu, Jun 12, 2003, Tony Gottfridsson wrote: > FreeBSD 4.5 malloc() never returns 0 and kills what seems to be > random processes, in my case apache seems to be the most likely > process to get killed first. You need to set resource limits on processes whose memory usage you wish to bound. See the 'memoryuse' limit in login.conf(5). See also: limit(1) and setrlimit(3). > This process killing is out of security bounds, ie. normal user > malloc()ing forever can kill processes owned by root The normal behavior is to kill the largest process. In FreeBSD 5.1, thanks to Wes, root can designate processes as critical so they will not be killed.