Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "J.O. Aho" Newsgroups: comp.lang.php Subject: Re: Exec Security Date: Sat, 01 Sep 2012 13:19:50 +0200 Lines: 23 Message-ID: References: <70901dbf-84a0-475d-a287-6fe420963592@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net tiBxcbbiruWCHJqzYd4bmg+dzp0ROT9jdg1VgVMheCNhjduzLRdhWN8qzSpYG+0jfo Cancel-Lock: sha1:LEKPyq4LfHsqrcHU+N56tnV1yow= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120807 Thunderbird/14.0 In-Reply-To: Xref: csiph.com comp.lang.php:6922 On 01/09/12 11:51, Ryan wrote: > That might just work to have a separate php.ini I might have to spin up a test server and try that out. You can have different php.ini, but still it's possible for someone to use that to do something else than you intended. > Having a DB queue that is processed by a cron job is kind of a last resort. > It would have to almost constantly be running or would have to wait too long to provision new vhosts. If you don't want to use cron jobs, then set up a service (you can write daemons with PHP) and use a message queue like zeromq, so the web interface sends a message to the daemon. Using the database is a simple way to do it, when you want to expand, you don't want to do the plesk way where you need to setup everything on every server which is used for hosting, you want a one place to administrate things from. -- //Aho