>Comment out the midgard bits and try again. Also check if your apache
>error log has any mention of a problem.
did this, and now i'm back to the original problem of not being able to load
midgard.so
>There's no need to comment out the line. If it isn't needed, it's
>harmless. Yes, you have to restart apache in order to activate changes
>that required a recompile. Have you recently upgraded php? I was
>lookinh at the same problem when I went from 405 to 406.
Yup...upgraded from 4.0.1 rpm (uninistalled it now) to 4.0.6 (from source).
>The extension_dir had changed but the change wasn't reflected in php.ini,
>so I was still loading the older module, not the one I just compiled.
I don't think that the changes in the php.ini file are being recognized when
i restart apache (using from binary: httpd stop/httpd start) because i'm
still getting that loading error for midgard.so. Is there another way to
get it to recognize this chage without rebooting? also, i don't have the
apachectl script on my machine...just an httpd script (in /etc/rc.d/init.d/)
that doesn't seem to work. Rebooting the server tends to upset people here!
Will i ever get midgard to work again?!
Aditya
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
