Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   5388 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

Apache::SIG(3)	      User Contributed Perl Documentation	Apache::SIG(3)

NAME
       Apache::SIG - Override apache signal handlers with Perl's

SYNOPSIS
	PerlFixupHandler Apache::SIG

DESCRIPTION
       When a client drops a connection and apache is in the middle of a
       write, a timeout will occur and httpd sends a SIGPIPE.  When apache's
       SIGPIPE handler is used, Perl may be left in the middle of it's eval
       context, causing bizarre errors during subsequent requests are handled
       by that child.  When Apache::SIG is used, it installs a different SIG-
       PIPE handler which rewinds the context to make sure Perl is back to
       normal state, preventing these bizarre errors.

       If you would like to log when a request was cancelled by a SIGPIPE in
       your Apache access_log, you can declare Apache::SIG as a handler (any
       Perl*Handler will do, as long as it is run before PerlHandler, e.g.
       PerlFixupHandler), and you must also define a custom LogFormat in your
       httpd.conf, like so:

       PerlFixupHandler Apache::SIG LogFormat "%h %l %u %t \"%r\" %s %b %{SIG-
       PIPE}e"

       If the server has noticed that the request was cancelled via a SIGPIPE,
       then the log line will end with 1, otherwise it will just be a dash.

CAVEATS
       The signal handler in this package uses the subprocess_env table of the
       main request object to supply the 'SIGPIPE' "environment variable" to
       the log handler. If you already use the key 'SIGPIPE' in your subpro-
       cess_env table, then you can redefine the key like this:

       $Apache::SIG::PipeKey = 'my_SIGPIPE';

       and log it like this:

       LogFormat "%h %l %u %t \"%r\" %s %b %{my_SIGPIPE}e"

AUTHORS
       Doug MacEachern and Doug Bagley

SEE ALSO
       perlvar(1)

perl v5.8.8			  2007-03-30			Apache::SIG(3)

                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 

Vote for polarhome