Quote:> Okay, so-- I've got this problem where the error_log in Apache/1.3b5
Entries written by _apache_ do follow some standard format(s).
>seems reluctant to log in the way I'd hope it would. For instance, I'm
>getting entries such as:
>date: not found
The error_log gets anything that any CGI/SSI-exec writes to STDERR, directly
with no place for Apache to reformat the strings.
Quote:> This provides me with no information as to what called date, why it's
>not finding it, whether it's being called from a parsed HTML file or a
>CGI-- anything useful.
It helps to rewrite your CGIs with good error handling, the case with SSI
is a little bit more tricky- if you try to run 'date' from a SSI 'exec',
what actually happens is that Apache spawns a shell process and tells the
shell it's supposed to execute something called 'date'. The shell then
searches the PATH for a program by that name, if it fails it writes a
string like the one you saw in your log file to STDERRR, which goes to the
Quote:> I've noticed people seeming to be able to set the logging level, so
>that it will log things at the [info] level or some such; I also
>remember "file not found" errors logging the referring URL that called
>the missing file. Those were very very useful features. How can I turn
>them on again?
If _Apache_ cannot find the file, it will log the problem very verbosely,
what happens when a program called from apache cannot find some sub-program
depends on the program and it's author (hint hint).
As far as CGI and HTML files not found, I prefer to use LogFormat to write
the access_log in NCSA's standardized Extended Logfile Format, then just
grep the access_log for result codes.