The behavior of mod_perl is that all stderr output gets sent to error.log. This appears not to be the case in mod_caml, unless I am overlooking something. Not sure how mod_perl does this. I'm not even sure how each module comes to have a separate stderr. Is each one a pthread? The standard process to process pipe in C involves making a strange combination of popen and fclose, which I don't remember off the top of my head. jefhen
I think you're overlooking something, because stderr is certainly getting written to the error_log file for me. There isn't even any specific mod_caml support for this. All Apache modules get this by default. Have you checked that your Apache config actually sets an error log file? - Rich.
On a related topic, what are other useful ways to get "warning" debug output, not on the fetched HTML page. I suppose I could just open a file.
To get warning and debug output, I always use prerr_endline.
ChriS: The cgi object of the CVS version of mod_caml possesses a #log method that can serve this purpose.
True enough, but all that does is call prerr_endline. If stuff being written to stderr isn't going to the log file, then there would seem to be something fairly fundamentally broken about Jeff's configuration. - Rich.
Okay, my bad. I didn't flush stderr. Duhh. I thought I had tried that. Thanks for the pointer. jefhen