Received: by taz.hyperreal.com (8.6.12/8.6.5) id LAA17358; Fri, 26 Jul 1996 11:25:17 -0700 Received: from sierra.zyzzyva.com by taz.hyperreal.com (8.6.12/8.6.5) with ESMTP id LAA17348; Fri, 26 Jul 1996 11:25:13 -0700 Received: from sierra.zyzzyva.com (localhost [127.0.0.1]) by sierra.zyzzyva.com (8.7.5/8.7.3) with ESMTP id NAA29078 for ; Fri, 26 Jul 1996 13:25:10 -0500 (CDT) Message-Id: <199607261825.NAA29078@sierra.zyzzyva.com> To: new-httpd@hyperreal.com Subject: Re: setrlimit config Directives In-reply-to: akosut's message of Fri, 26 Jul 1996 11:06:51 -0700. X-uri: http://www.zyzzyva.com/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Jul 1996 13:25:10 -0500 From: Randy Terbush Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com > On Fri, 26 Jul 1996, Randy Terbush wrote: > > > Please review the following patch. > > > > These changes add support for RLimitCPU, RLimitMEM, and RLimitNPROC. > > I don't know about the internals, but I'd perfer the directive functions > themselves be outside the #ifdefs, not inside. That way you can put > "RLimitCPU" in a config file of a machine that doesn't support it, and it > could tell you that it doesn't support it, instead of "Unknown directive" > or whatnot. (which could be rather confusing to someone who doesn't quite > understand). > > -- Alexei Kosut The Apache HTTP Server > http://www.nueva.pvt.k12.ca.us/~akosut/ http://www.apache.org/ Good idea. Change made. I'm going to see if I can address Ben's concerns here. The patch as it stands would solve some of the problems that have been reported lately.