Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: softfail (athena.apache.org: transitioning domain of
 adam.prime@utoronto.ca does not designate 216.220.44.220 as permitted sender)
Message-ID: <49AC0256.4070003@utoronto.ca>
Date: Mon, 02 Mar 2009 10:59:18 -0500
From: Adam Prime <adam.prime@utoronto.ca>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Michael Peters <mpeters@plusthree.com>
CC: Perrin Harkins <pharkins@gmail.com>,
 Matthew Lenz <matthew@nocturnal.org>,
 mod_perl list <modperl@perl.apache.org>
Subject: Re: get backtrace emailed when code dies running under
 	ModPerl::RegistryPrefork?
References: <1236005687.5979.12.camel@mlenz-desktop>
 <66887a3d0903020720u7b43dbdeude1e8574c7e60980@mail.gmail.com>
 <49ABFBDF.5010403@plusthree.com>
In-Reply-To: <49ABFBDF.5010403@plusthree.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Michael Peters wrote:
> 
> You don't even need to use a __DIE__ handler. mod_perl will place any 
> runtime errors into $r->notes('error-notes'). I don't like my errors 
> going to the browser (only really works if your content is HTML anyway) 
> but for the email I usually use an Apache cleanup handler. That way it 
> gets sent after the client request has returned, so they don't have to 
> wait on it.
> 

This was news to me, so i went to the docs.  According to them, you have 
to explicitly enable this behavior.  see:

http://perl.apache.org/docs/2.0/api/Apache2/Log.html#C_Apache2__Const__LOG_TOCLIENT_

Is that still accurate?

Adam