Re: startup sequencing issue with php_admin_value disable_functions?

> At 09:30 24-10-01, Rasmus Lerdorf wrote: > > > At 07:55 24-10-01, Rasmus Lerdorf wrote: > > > >php_admin_value disable_functions does not work. Works fine from php.ini. > > > > > > It's not supposed to work, it can only work from php.ini. > > > >Why? > > Look at the code... It's really designed to be a one-time thing, rather > than something that can be easily turned on/off - if it was supported on a > per-virtual-host basis. It can be implemented, but it would require quite > a bit of coding, as this functionality is simply not there right now. I did look at the code and I still don't understand. It's not like httpd.conf directives can be run multiple times under normal circumstances. If we exposed it to .htaccess as well, that would be a different story. Just seems to me like if the php_disable_functions() call was done after httpd.conf had a chance to overwrite the php.ini value this would work. Although looking at zend_disable_function(), why can't this be called in two stages? I can understand not being able to re-enable a function, but making php.ini and httpd.conf cumulatively disable functions seems like it should work. -Rasmus