Module register_hooks and config seems to be called twice when Apache starts up?

2012-07-01 Thread ohaya
Hi, I have the following in my module: module AP_MODULE_DECLARE_DATA my_module = { STANDARD20_MODULE_STUFF, NULL, /* dir config creater */ NULL, /* dir merger --- default is to overrid

Re: Module register_hooks and config seems to be called twice when Apache starts up?

2012-07-01 Thread Eric Covener
On Sun, Jul 1, 2012 at 11:48 AM, wrote: > Hi, > > I have the following in my module: > > > module AP_MODULE_DECLARE_DATA my_module = > { >     STANDARD20_MODULE_STUFF, >     NULL,                                                  /* dir config > creater */ >     NULL,                            

Re: Module register_hooks and config seems to be called twice when Apache starts up?

2012-07-01 Thread ohaya
Eric Covener wrote: > On Sun, Jul 1, 2012 at 11:48 AM, wrote: > > Hi, > > > > I have the following in my module: > > > > > > module AP_MODULE_DECLARE_DATA my_module = > > { > >     STANDARD20_MODULE_STUFF, > >     NULL,                                                  /* dir config > > c

"Best practices" or recommendations for logging from a module?

2012-07-01 Thread ohaya
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 various things. I am somewhat loath t

Re: "Best practices" or recommendations for logging from a module?

2012-07-01 Thread ohaya
[email protected] 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 outpu

Re: "Best practices" or recommendations for logging from a module?

2012-07-01 Thread Joe Lewis
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, wrote: > > [email protected] wrote: > > Hi, > > >

Re: "Best practices" or recommendations for logging from a module?

2012-07-01 Thread ohaya
Joe Lewis 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, wrote: > Jo

Re: "Best practices" or recommendations for logging from a module?

2012-07-01 Thread ohaya
[email protected] wrote: > > Joe Lewis 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

Re: "Best practices" or recommendations for logging from a module?

2012-07-01 Thread ohaya
[email protected] wrote: > > [email protected] wrote: > > > > Joe Lewis 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

Re: "Best practices" or recommendations for logging from a module?

2012-07-01 Thread Joe Lewis
On 07/01/2012 12:55 PM, [email protected] wrote: [email protected] wrote: [email protected] wrote: Joe Lewis 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 lo

Re: "Best practices" or recommendations for logging from a module?

2012-07-01 Thread ohaya
Joe Lewis wrote: > On 07/01/2012 12:55 PM, [email protected] wrote: > > [email protected] wrote: > > > >> [email protected] wrote: > >> > >>> Joe Lewis wrote: > >>> > Jim, you could use the log_error funtion all the time. Log_perror javits > logging associate

Re: "Best practices" or recommendations for logging from a module?

2012-07-01 Thread Joe Lewis
On 07/01/2012 01:53 PM, [email protected] wrote: Joe Lewis wrote: On 07/01/2012 12:55 PM, [email protected] wrote: [email protected] wrote: [email protected] wrote: Joe Lewis wrote: Jim, you could use the log_error funtion all the time. Log_p

Re: "Best practices" or recommendations for logging from a module?

2012-07-01 Thread ohaya
Joe Lewis wrote: > On 07/01/2012 01:53 PM, [email protected] wrote: > > Joe Lewis wrote: > > > >> On 07/01/2012 12:55 PM, [email protected] wrote: > >> > >>> [email protected] wrote: > >>> > >>> > [email protected] wrote: > > > > Joe Lewis

Re: "Best practices" or recommendations for logging from a module?

2012-07-01 Thread Joe Lewis
On 07/01/2012 05:28 PM, [email protected] wrote: Joe Lewis wrote: On 07/01/2012 01:53 PM, [email protected] wrote: Joe Lewis wrote: On 07/01/2012 12:55 PM, [email protected] wrote: [email protected] wrote: [email protected] wrote: