Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 4364 invoked by uid 6000); 1 Jan 1998 23:57:51 -0000 Received: (qmail 4189 invoked from network); 1 Jan 1998 23:57:47 -0000 Received: from localhost.hyperreal.org (HELO brianb.organic.com) (127.0.0.1) by localhost.hyperreal.org with SMTP; 1 Jan 1998 23:57:47 -0000 Message-Id: <3.0.3.32.19980101154854.007ccdf0@localhost> X-Sender: brian@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 01 Jan 1998 15:48:54 -0800 To: new-httpd@apache.org From: Brian Behlendorf Subject: Re: worth fixing "read headers forever" issue? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org At 11:04 PM 12/31/97 -0700, Marc Slemko wrote: >I am doubtful that rlimits can be used usefully. Why not? Because rlimits aren't inherited by the children from the parent? Because of x-platform variance in implementation? If rlimit isn't standardized widely enough yet, maybe instead of putting counters on every possible source of network input, we should emulate rlimit functionality inside Apache? So we're controlling the memory and CPU consumption as a whole instead of within isolated areas. Side benefit: we'd get resource limiting on platforms without any type of rlimit functionality, like NT. Downside: marginal server bloat & overhead. Brian "All applications eventually expand their feature set until they can read mail." --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- specialization is for insects brian@organic.com