Hi,
Yes, I got the errors on stderr too, usually (for example, if the name
of the module was mispelled, the error was shown properly).
As I told you, this was a strange situation. The modules could be found
the first time the configuration was processed (and their constructors
were called, as I could check), but it seems like the same wasn't
happening AFTER the child httpd processes were spawned. The reason I
couldn't see the error messages in this case is that the children
processes were daemonized, and thereby dettached from the terminal, I
guess. It was with strace that I could see the calls to write() with the
error messages, messages which I'd never see otherwise.
Anyway, it still seems weird to me that the first time the modules can
be found, but not the second, after the fork(). And that, in
single-process mode, they'd be found both times...
My configuration is exactly the same as in your examples, I sent it to
you in one of our first messages, but I'll re-send it if you want.
Please let me know if you find an explanation for all this... thanks!
Pachi.
On Mon, 2002-09-02 at 15:17, John K.Sterling wrote:
> Great -
>
> But i can't reproduce this. when i try to load a non-existent config
> file i get an error to stderr (not to the log file)
>
> Error Loading CPP SO foobar into server: cannot create object file
> image or add library
>
> do you get something different? or were you not looking at
> stdout/stderr? lemme know more specifically what your configuration
> looks like and i'll try to reproduce and fix it.
>
> glad to know its all working for you.
>
> sterling
>
|