From new-httpd-owner-new-httpd-archive=hyperreal.org@apache.org Thu Jun 25 20:34:48 1998 Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 19897 invoked by uid 6000); 25 Jun 1998 20:34:47 -0000 Received: (qmail 19870 invoked from network); 25 Jun 1998 20:34:44 -0000 Received: from unknown (HELO gensym-nt2.gensym.com) (192.156.185.15) by taz.hyperreal.org with SMTP; 25 Jun 1998 20:34:44 -0000 Received: by gensym-nt2.gensym.com with Internet Mail Service (5.0.1458.49) id ; Thu, 25 Jun 1998 16:31:06 -0400 Message-ID: From: Ben Hyde To: "'new-httpd@apache.org'" Subject: RE: -X oddity Date: Thu, 25 Jun 1998 16:31:05 -0400 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org I suspect we have all been there! It might be better as you suggest, but without of changing the code, doc, and the minds of all the people who know how it currently is you can set MaxRequestsPerChild to zero, and you can now even do it from the command line via -C. - ben hyde On Thursday, June 25, 1998 4:06 PM, Dan Jacobowitz [SMTP:drow@false.org] wrote: > I eventually managed to track the cause of the follwing, and became > much less panicked, but I really don't think this should happen: > > I was debugging some mod_perl things, and because of a few weakness > with reloading changed code, I ran the server -X so I could more quickly > kill/restart it. After thirty requests, it died. For some reason, if > perl had been used at all in the session it exited with 'Aborted' > instead of silently - no idea why on that one. But the cause was > MaxRequestsPerChild. This is just enough to load two pages or so if > they are heavy on images, leaving -X a little bit useless. Shouldn't > this be ignored in single-server mode? > > Dan >