In fact, I was using 5.2.11 already, my bad I looked at the wrong package. On Mon, Nov 2, 2009 at 7:43 PM, Site Mail <[email protected]> wrote:
> Thank you for the quick answer. > > In fact, in info.php I see the configuration is taken from the same file in > both cases (the right file) So I do not know why in "top" the php.cgi > processes shows up using more than 100M sometimes. > > I just set up the fascgi as tcp (I did not upgrade from old version of > wizzards). > > By the way, I am using php 5.2.6, maybe this is the problem, I am going to > try with dotdeb repository, which is 5.2.11, and see if the issue stops. > > THanks for the help. > > > On Mon, Nov 2, 2009 at 7:34 PM, Alvaro Lopez Ortega > <[email protected]>wrote: > >> On 02/11/2009, at 11:41, Site Mail wrote: >> >> I just found out that passing -c /etc/php5/cgi/php.ini as the argument in >>> the interpreter (/usr/bin/php-cgi -c /etc/php5/cgi -b >>> /tmp/cherokee-php.socket) seems to comply with the limits I established in >>> the php.ini. >>> >>> The thing is that I do not know if it is a problem my configuration file, >>> or it is problem of the default behavior of cherokee not picking the right >>> file. >>> >> >> Actually, it looks like a PHP installation issue. Cherokee launches >> php-cgi, it's up the the interpreter the configuration file it uses. >> >> By the way, I'd strongly encourage you to set up php-cgi to use a TCP >> socket instead of a Unix socket; experience has taught us, that's a better >> way to run it. >> >> Cheers! >> >> -- >> Octality >> http://www.octality.com/ >> >> >
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
