Aditya Dhekney wrote:
> >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
So what does the error message say?
If you comment out midgard.so from php.ini, does everything work as usual?
If you comment out midgard.so from php.ini, but leave mod_midgard active
in httpd.conf, does apache work as usual (except midgard requests)?
> Yup...upgraded from 4.0.1 rpm (uninistalled it now) to 4.0.6 (from source).
I assume midgard-php4 was recompiled since the rpm version was
uninstalled?
> 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.
Exactly what error are you getting? Is the updated extension_dir being
recognized? Try setting it to a bogus value and check that it is
trying to load midgard from there. You can also change a setting like
allow_url_fopen or whatnot and see if it changes if you call phpinfo.
> Is there another way to get it to recognize this chage without rebooting?
It doesn't require a reboot.
> 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!
Apache is from rpm, right? If so, the script in /etc/rc.d/init.d/ is
the right script to stop and start apache.
Emile
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
