> That's right, this was missing! (for Armand: it was a > fresh install, so the outcommented line was not > present indeed) But when I add the line > extension = midgard.so > to php.ini (btw: there is indeed a midgard.so located > in my /usr/lib/php/extensions/midgard.so directory), > no php files are not found anymore! > For any simple php file I get a "the page cannot be > displayed" error (IE), or "the document contained no > data" (netscape), but still a code 200 in my apache > access log.
And with debug logging? Does it say anything in the error log? > and another thing: whether the extension = midgard.so > in php.ini is outcommented or not, I every time get > the following lines in /var/log/httpd/error_log when > I restart the http server ( /usr/sbin/apachectl > restart): > > [Mon Nov 12 15:08:05 2001] [notice] caught SIGTERM, >shutting down > [Mon Nov 12 15:08:06 2001] [error] Cannot remove > module mod_midgard.c: not found > in module list > [Mon Nov 12 15:08:10 2001] [error] Cannot remove > module mod_midgard.c: not found > in module list Never seen this, but I'd verify it's pointing at the right module, and that the LoadModule/AddModule statements for mod_midgard are in an order that resembles the other modules in apaches configuration. We use apxs to insert out config lines but apxs is pretty fragile when the config file gets complex. Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
