virtual host error log. die printed it to the
>> virtual host error log.
>
> Yeah, that was bad advice. You should probably use Apache2::Log for
> this instead:
> http://perl.apache.org/docs/2.0/api/Apache2/Log.html
>
> - Perrin
>
>
--
View thi
On Fri, Sep 12, 2008 at 6:38 PM, kropotkin <[EMAIL PROTECTED]> wrote:
> Just one problem though - print STDERR is printing the message to the main
> server error log not the virtual host error log. die printed it to the
> virtual host error log.
Yeah, that was bad advice. You should probably use
ge and replace it with my own (I found out it takes
>> text
>> as well as a file). I just pass it a period, and that's it.
>
> That's not a good solution. What if there was an unexpected error in
> some other code? You would never know.
>
> - Perrin
>
&
On Fri, Sep 12, 2008 at 5:14 PM, kropotkin <[EMAIL PROTECTED]> wrote:
> True; I could pass return values
> back up the chain and at the top-level if there was a problem do return "OK"
> there to cancel execution without generating a 500 error but this would be a
> pain to manage.
Then catch the di
>
> Make that:
>
> print STDERR $error_message;
> return OK();
>
> - Perrin
>
>
--
View this message in context:
http://www.nabble.com/die-problem-in-mod_perl-tp19462854p19464258.html
Sent from the mod_perl - General mailing list archive at Nabble.com.
On Fri, Sep 12, 2008 at 3:46 PM, kropotkin <[EMAIL PROTECTED]> wrote:
> Then I want to stop the script executing any further and ideally to write to
> the server error logs. So the last line of my error handling routine is:
> die $error_message.
Make that:
print STDERR $error_message;
return OK()
plete
your request" message, which I don't want as I've already printed my own
user friendly message.
How can I stop this behaviour?
with thanks
Kropotkin
--
View this message in context:
http://www.nabble.com/die-problem-in-mod_perl-tp19462854p19462854.html
Sent from th
