Am 17.01.2015 um 05:45 schrieb Rainer Jung:
Hi Jan,
Am 23.09.2014 um 13:14 schrieb [email protected]:
Author: jkaluza
Date: Tue Sep 23 11:14:09 2014
New Revision: 1626978
URL: http://svn.apache.org/r1626978
Log:
mod_cgi: log cgi script stderr to ScriptLog, use APLOGNO for
log_scripterror
errors.
Modified:
httpd/httpd/trunk/docs/log-message-tags/next-number
httpd/httpd/trunk/modules/generators/mod_cgi.c
...
Modified: httpd/httpd/trunk/modules/generators/mod_cgi.c
URL:
http://svn.apache.org/viewvc/httpd/httpd/trunk/modules/generators/mod_cgi.c?rev=1626978&r1=1626977&r2=1626978&view=diff
==============================================================================
--- httpd/httpd/trunk/modules/generators/mod_cgi.c (original)
+++ httpd/httpd/trunk/modules/generators/mod_cgi.c Tue Sep 23 11:14:09
2014
...
@@ -210,8 +211,7 @@ static apr_status_t log_script_err(reque
if (newline) {
*newline = '\0';
}
- ap_log_rerror(APLOG_MARK, APLOG_ERR, 0, r, APLOGNO(01215)
- "%s", argsbuffer);
+ log_scripterror(r, conf, r->status, 0, APLOGNO(01215),
argsbuffer);
}
return rv;
This fix and its backport to 2.4 seems to be incomplete. I can see the
STDERR output of nph-stderr.pl in the test framework now going to the
ScriptLog (after this patch, e.g. for 2.4.11) but only for some
platforms. On my Solaris 10 Sparc system it works, but on Solaris 8
Sparc or RHEL 6 the STDERR output still goes to the normal error log. I
don't expect it to be a real platform issue, but more a timing issue or
similar.
The problem does not occur for mod_cgi but only for mod_cgid.
If both are being build and installed, then the test framework will load
both. It seems that for some reason my Solaris 10 Sparc system is the
only one, on which the requests are then actually executed by mod_cgi,
on all other platforms they are being executed by mod_cgid, which does
not write stderr output to the ScriptLog but instead to STDERR which is
captured by the error log.
So the fix to mod_cgi is *not* incomplete, but we should also fix it for
mod_cgid.
Regards,
Rainer
