Commit a3eac7d9 authored by Marc Slemko's avatar Marc Slemko
Browse files

Clarify that the ScriptLog is opened by the child processes so 

permissions need to be set appropriately.  Perhaps wouldn't hurt
to put an error in the error_log if it can't be opened.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@78111 13f79535-47bb-0310-9956-ffa450edef68
parent 44c5b2dd

docs/manual/mod/mod_cgi.html

+13 −8
Original line number Diff line number Diff line
@@ -114,14 +114,19 @@ anything on standard output or standard error). 
<b>Status:</b> mod_cgi

<p>



The <tt>ScriptLog</tt> directive sets the CGI script error logfile. If

no

ScriptLog is given, no error log is created. If given, any CGI errors

are

logged

into the filename given as argument. If this is a relative file or

path it is

taken relative to the server root.

The <tt>ScriptLog</tt> directive sets the CGI script error logfile.

If no ScriptLog is given, no error log is created. If given, any

CGI errors are logged into the filename given as argument. If this

is a relative file or path it is taken relative to the server root.



<P>This log will be opened as the user the child processes run as,

ie. the user specified in the main <A HREF="core.html#User">User</A>

directive.  This means that either the directory the script log is

in needs to be writable by that user or the file needs to be manually

created and set to be writable by that user.  If you place the

script log in your main logs directory, do <STRONG>NOT</STRONG>

change the directory permissions to make it writable by the user

the child processes run as.</P>



<p>Note that script logging is meant to be a debugging feature when

writing CGI scripts, and is not meant to be activated continuously on