<br><br><div class="gmail_quote">On Mon, Jan 18, 2010 at 9:05 AM, Steve Kleiman <span dir="ltr"><<a href="mailto:steve@prodhub.com">steve@prodhub.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Thanks for all the feedback on how to log from within a schema. Log4perl is my hero.<br>
<br>
I'm still looking for a way to capture runtime errors and ideally email them out in addition to logging to a file.<br></blockquote><div><br>I use log4perl to send "error" level messages to an additional log file. Then I use cron to check for errors every few minutes and send a notification email. I like that better than the possibility of hundreds of processes cranking out mail at the same time. <br>
<br>The plan is to move to a logging server to centralize this a bit more.<br></div><div><br><br></div></div><br clear="all"><br>-- <br>Bill Moseley<br><a href="mailto:moseley@hank.org">moseley@hank.org</a><br>