Date: Mon, 29 Jun 1998 17:08:13 -0700 (PDT)
From: Dean Gaudet <dgaudet@arctic.org>
To: new-httpd@apache.org
Subject: Re: Question about ScriptLog and CGI output to stderr...
In-Reply-To: <5040300017725265000002L052*@MHS>
Message-ID: <Pine.LNX.3.96dg4.980629170604.706M-100000@twinlark.arctic.org>
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

If someone is playing with ScriptLog, it's worthwhile noting a low
numbered PR... where I note that ScriptLog produces a deadlock:  if the
script writes too much to stderr, it'll block.  Meanwhile httpd is reading
from the script's stdout... and not touching the stderr. 

I don't really find it acceptable to allow unformatted CGI error data in
the error log... but that's just how it's always been. 

Ideally each line of error output would be prefixed before going into the
error log. 

Kind of a pain to solve in 1.3 though... at least that's how it's seemed
each time I've gone in to consider fixing it.  For apache-nspr it could be
done with an I/O layer. 

Dean

On Mon, 29 Jun 1998, W G Stoddard wrote:

> I've been looking at PRs 2408 and 2429 and have a few questions about CGI error
> logging and the ScriptLog directive.
> 
> Information (written to stdout or stderr) is recorded in the ScriptLog only
> when the script exists with error status, otherwise this information is
> discarded...  True?  Should this same information also be written to the
> errorlog file?  What should happen to information written to stderr when
> ScriptLog is not defined?  Is it acceptable to allow unformatted CGI error data
> to be written to the Apache error log?
> 
> Just want to make sure I understand how this should work before jumping into
> the PRs.
> 
> 
> Thanks,
> Bill Stoddard
> wgstodda@us.ibm.com
>