[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-modperl
Subject:    Re: logging SIGPIPE
From:       Ian Kallen <ian () GAMESPOT ! COM>
Date:       1998-03-25 18:12:52
[Download RAW message or body]

Support for logging this with more detail than the standard error_log
entries would be great.  A daily run of stats on requests that people lost
patience with might be really informative but the present error_log
entries that Apache emits aren't very helpful.

On Wed, 25 Mar 1998, Doug MacEachern wrote:
:Doug Bagley wrote:
:
:> I'd like to add an indicator to the access_log line that shows when the
:> server has received a SIGPIPE (as in client has hit STOP).
:>
:> I have a hack which does the job, basically I added a custom LogFormat in
:> my httpd.conf (LogFormat "... %{STOP}e ..."), I stashed the Apache request
:> object at the start of the request, and I created a replacement to
:> Apache::SIG to set $r->subproces_env('STOP' => 1); when the SIGPIPE is
:> caught.
:>
:> This works, but I was wondering if there was an easier way to do it?  Any
:> ideas?
:
:Seems general enough that Apache::SIG's PIPE catch should indicate this has
:happened, I'd be happy to apply a patch from you that does that.
:
:-Doug
:

--
Ian Kallen                                              ian@gamespot.com
"I try to drink a bottle of whiskey a day. Whether I need it or not."
                                        - Lemmy

[prev in list] [next in list] [prev in thread] [next in thread]