Other stuff removed ... > > > > > -----Original Message----- > > > From: [email protected] [mailto:blueonyx- > [email protected]] > > > 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?
OK, you should set this in your sitexx.include file. It does not go into a directory or location container. Here is an example of how I set memory limits: php_admin_value memory_limit 32M Just like that and it works like a charm. These are helpful pages: http://us3.php.net/manual/en/ini.list.php and http://us3.php.net/manual/en/configuration.changes.php -Stephanie _______________________________________________ Blueonyx mailing list [email protected] http://www.blueonyx.it/mailman/listinfo/blueonyx
