Re: How to write to log from own functions?

2019-07-31 Thread Bill Moo
Thanks again Eric, I did suspect that that would be the solution. I feel another parameter coming on. On Wed, 31 Jul 2019 at 14:49, Eric Covener wrote: > > On Wed, Jul 31, 2019 at 9:44 AM Bill Moo wrote: > > > > As the subject says really. How can I write to the log from my own > > functions

Re: How to write to log from own functions?

2019-07-31 Thread Eric Covener
On Wed, Jul 31, 2019 at 9:44 AM Bill Moo wrote: > > As the subject says really. How can I write to the log from my own > functions I see nothing (obvious) in the documentation on how to do > this. The functions that are there require a server_rec, connection or > pool pointer, that I don’t have

How to write to log from own functions?

2019-07-31 Thread Bill Moo
As the subject says really. How can I write to the log from my own functions I see nothing (obvious) in the documentation on how to do this. The functions that are there require a server_rec, connection or pool pointer, that I don’t have access to in my own functions. -- Bill

Re: [EXTERNAL] Re: No content returned from directive handler sample.

2019-07-31 Thread Bill Moo
For those interested I have now fixed this thanks to a bit of logging and the culprit was in fact this line: if(!r->handler || strcmp(r->handler, "configHandler")) return(DECLINED); the string being offered in the r->handler was in fact confighandler so the comparison was failing and declining