[BlueOnyx:06144] Re: Problems with PHP.INI and memory_limit

[Darrell D. Mobley]

> -----Original Message-----
> From: blueonyx-bounces at blueonyx.it [mailto:blueonyx-bounces at blueonyx.it]
> On Behalf Of Michael Stauber
> Sent: Thursday, December 16, 2010 3:02 PM
> To: BlueOnyx General Mailing List
> Subject: [BlueOnyx:06139] Re: Problems with PHP.INI and memory_limit
> 
> That can sometimes happen. The RC start/stop script for Apache tries 
> to stop Apache during a restart, before it starts it again. But if the
> "stop" command doesn't kill off all "httpd" processes, a (re)start can
> fail. In that case a reboot fixes thing. Or manually issuing a "killall
> -9 httpd" as "root" does the job as well. But then you have to manually
> (re)start both AdmServ.

But why is the memory limit set in the site's PHP GUI screen being ignored
and using the server's main PHP.INI file in the first place?  Isn't the
point of having memory limit options in each site's GUI to allow them to be
set there and relied upon?