>From the 'Practical mod_perl' book, When a user presses the Stop or Reload button, the current socket connection is broken (aborted). If the reading of the request's data is completed and the code does its processing without writing anything back to the client, the broken connection won't be noticed. When an attempt is made to send at least one character to the client, the broken connection will be noticed and the SIGPIPE signal (Broken Pipe) will be sent to the process. The program can then halt its execution and perform all its cleanup requirements.
So I think you should be careful to handle the "User Pressed Stop Button" case. Also see here pls: http://perl.apache.org/docs/1.0/guide/debug.html#Handling_the__User_pressed_Stop_button__case -----Original Message----- >From: Octavian Rasnita <[EMAIL PROTECTED]> >Sent: Feb 17, 2006 7:51 AM >To: modperl@perl.apache.org >Subject: Broken pipe > >Hi, > >I have seen in the error log of Apache the following line (for more times, >exactly the same): >[Fri Feb 17 13:58:04 2006] [info] [client 83.103.222.187] (32)Broken pipe: >core_output_filter: writing data to the network > >I can see [info]. Do this means that it is not a real error but just a >warning? >Why does it appear? > >I have followed the suggestions, searched the web, and I have also put in >httpd.conf: > >EnableSendfile Off > >But these errors continue to appear. > >Teddy > -- Jeff Pang NetEase AntiSpam Team http://corp.netease.com
