On Sat 04 Apr 2009, E R wrote:
One operational issue with this is that if the logger process dies,
existing httpd processes will get a SIGPIPE signal on subsequent
writes. Restarting the logger process does not restore the lost
connections.
On Fri, Apr 3, 2009 at 12:38 PM, Torsten Foertsch
On Fri, Apr 3, 2009 at 1:22 PM, E R pc88m...@gmail.com wrote:
I want to send all error output to a process for specialized logging.
I know that you can use CustomLog with a pipe. However, will that
capture output from things like 'print STDERR ...' or if an XS module
directly writes to stderr?
Hi Torsten,
On Sun, Apr 5, 2009 at 4:13 AM, Torsten Foertsch
torsten.foert...@gmx.net wrote:
And later on it does not check the return code when writing the log:
httpd-2.2.11/server/log.c:682:
apr_file_puts(errstr, logf);
apr_file_flush(logf);
My concern is about what happens
Jeff Pang wrote:
How google achieve this? Thanks.
Completely off topic. Next time please label your subject with an OT so we're
know. But I suspect they are using flash (which most music players use) and
flash has it's own cookie system which is outside of the browsers.
--
Michael Peters
Hello,
if possible I try to develop on Windows, then deploy on Linux or Solaris
for production. This worked very well in the past with a self compiled
environment (VC6). But as some components are rather old by now I would
like to recompile with recent versions of apache, perl, mod_perl,
openssl
Author: phred
Date: Mon Apr 6 04:27:14 2009
New Revision: 762204
URL: http://svn.apache.org/viewvc?rev=762204view=rev
Log:
Fix documentation errors, and find subtle bug where mp1 was looking
for mod_perl1.pm. Simplify this by using distinct monikers mod_perl
and mod_perl2 instead of trying to
