If you use Apache's logging facilities (say for level debug). Apache will
handle the concurrency/serializing for you.
You might also look at using syslog
-Original Message-
From: Edmar Edilton da Silva [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 08, 2000 2:46 PM
To: [EMAIL
On Fri, 8 Dec 2000, Edmar Edilton da Silva wrote:
Hi all,
I have installed on my machine the mod_perl module and exists a lots
perl scripts running under mod_perl. I am doing some tests and I need
that all call to these perl scripts write in a log file. How can there
are a lots
I don't know if this helps but when you log something add the process ID to
the log message. Then you should be able to trace what process is running
what, look at :
http://httpd.apache.org/docs/mod/mod_log_config.html#formats
to tell you how to set up custom log formats, %p gives you the pid,
On Fri, 8 Dec 2000, Jerrad Pierce wrote:
If you use Apache's logging facilities (say for level debug). Apache will
handle the concurrency/serializing for you.
If I remember correctly only if the size of a single
warn/print(STDERR,...) 4k, if you are talking about manually logging
thru
...
-Original Message-
From: Stas Bekman [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 08, 2000 3:51 PM
To: Jerrad Pierce
Cc: mod_perl list
Subject: RE: Concurrenty access to a log file!!!
On Fri, 8 Dec 2000, Jerrad Pierce wrote:
If you use Apache's logging facilities (say for level
debug
