Return-Path: <new-httpd-owner-new-httpd-archive=hyperreal.org@apache.org>
Delivered-To: new-httpd-archive@hyperreal.org
Received: (qmail 11956 invoked by uid 6000); 9 Nov 1997 15:45:06 -0000
Received: (qmail 11949 invoked from network); 9 Nov 1997 15:45:05 -0000
Received: from alcor.process.com (192.42.95.16)
  by taz.hyperreal.org with SMTP; 9 Nov 1997 15:45:05 -0000
Date: Sun, 9 Nov 1997 10:44 -0400
From: COAR@PROCESS.COM (Rodent of Unusual Size)
Message-Id: <009BD084E58F213C.59B0@PROCESS.COM>
To: new-httpd@apache.org
Subject: Re: general/1376: Server stops servicing requests when log disk is
 full (fwd)
X-VMS-To: SMTP%"new-httpd@apache.org"
X-VMS-Cc: COAR
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

>From the fingers of Jim Jagielski flowed the following:
>
>This is pretty similar to the "Server stops servicing requests when
>the computer blows up" bug report...
>
>Marc Slemko wrote:
>> 
>> Erm.... exactly what are we supposed to do here?

    Stop logging: no, mustn't compromise the audit trail.
    Delete files: nope.

    My vote is to return a 500 (or, better yet, a 503) and log the
    problem through syslog (if available).

    The problem is detecting the condition before servicing the request..

    #ken    P-)}