(crazyinsomniac) Re: Reading the last fews lines of the Apache error log

I agree with the monks above. But if you don't want to reveal line numbers and maybe some variable names, why don't you just keep your own error log. Check out this for details.

update:
DOUGH!!! I totally misread the question. kickstart is right just edit your httpd.conf file, i just did this the other day. It's pretty easy, but you will need to reload the server if you messup.

I suggest IndigoPerl if you got windows. It loads pretty fast and works well. It is very good for testing. Here's a review.

Even abbot's make mistakes, what can you do.

"cRaZy is co01, but sometimes cRaZy is cRaZy".
- crazyinsomniac

Comment on (crazyinsomniac) Re: Reading the last fews lines of the Apache error log

Replies are listed 'Best First'.
Re: Re: Reading the last fews lines of the Apache error log by Kickstart (Pilgrim) on Feb 06, 2001 at 04:50 UTC
Not sure what you were pointing to. You could also just call something like this in httpd.conf: ErrorDocument 500 /cgi-bin/error500.cgi ...in a previous job I wrote a script like this for 404 errors that tracked the error, logged it, kept some statistics, then emailed the appropriate webmaster based on the URL (in this case the domain name) with the error (containing the $ENV{'HTTP_REFERER'} in case it was helpful to track down the error). Kickstart	[reply]

Replies are listed 'Best First'.

Re: Re: Reading the last fews lines of the Apache error log
by Kickstart (Pilgrim) on Feb 06, 2001 at 04:50 UTC

You could also just call something like this in httpd.conf: ErrorDocument 500 /cgi-bin/error500.cgi

...in a previous job I wrote a script like this for 404 errors that tracked the error, logged it, kept some statistics, then emailed the appropriate webmaster based on the URL (in this case the domain name) with the error (containing the $ENV{'HTTP_REFERER'} in case it was helpful to track down the error).

Kickstart

[reply]