oh...@cox.net wrote:
Hi,
I'm working on my 1st module, and everything seems to be working so far. At
this point, since it's a first module, and I've been doing lots of debugging,
mostly running Apache in single process mode (-k start -X), I've only been
using printf to output
Jim, you could use the log_error funtion all the time. Log_perror javits
logging associated with a pool, and log_rerror is for requests. If
possible, use log_rerror, because it puts the up address, etc into the logs.
Joe
On Jul 1, 2012 10:56 AM, oh...@cox.net wrote:
oh...@cox.net wrote:
Joe Lewis jle...@silverhawk.net wrote:
Jim, you could use the log_error funtion all the time. Log_perror javits
logging associated with a pool, and log_rerror is for requests. If
possible, use log_rerror, because it puts the up address, etc into the logs.
Joe
On Jul 1, 2012 10:56 AM,
oh...@cox.net wrote:
Joe Lewis jle...@silverhawk.net wrote:
Jim, you could use the log_error funtion all the time. Log_perror javits
logging associated with a pool, and log_rerror is for requests. If
possible, use log_rerror, because it puts the up address, etc into the logs.
oh...@cox.net wrote:
oh...@cox.net wrote:
Joe Lewis jle...@silverhawk.net wrote:
Jim, you could use the log_error funtion all the time. Log_perror javits
logging associated with a pool, and log_rerror is for requests. If
possible, use log_rerror, because it puts
On 07/01/2012 12:55 PM, oh...@cox.net wrote:
oh...@cox.net wrote:
oh...@cox.net wrote:
Joe Lewisjle...@silverhawk.net wrote:
Jim, you could use the log_error funtion all the time. Log_perror javits
logging associated with a pool, and log_rerror is for
Joe Lewis j...@joe-lewis.com wrote:
On 07/01/2012 12:55 PM, oh...@cox.net wrote:
oh...@cox.net wrote:
oh...@cox.net wrote:
Joe Lewisjle...@silverhawk.net wrote:
Jim, you could use the log_error funtion all the time. Log_perror javits
On 07/01/2012 01:53 PM, oh...@cox.net wrote:
Joe Lewisj...@joe-lewis.com wrote:
On 07/01/2012 12:55 PM, oh...@cox.net wrote:
oh...@cox.net wrote:
oh...@cox.net wrote:
Joe Lewisjle...@silverhawk.net wrote:
Jim, you could use
On 07/01/2012 05:28 PM, oh...@cox.net wrote:
Joe Lewisj...@joe-lewis.com wrote:
On 07/01/2012 01:53 PM, oh...@cox.net wrote:
Joe Lewisj...@joe-lewis.com wrote:
On 07/01/2012 12:55 PM, oh...@cox.net wrote:
oh...@cox.net wrote:
