22 messages in ru.sysoev.nginxRe: php-fastcgi and memory leaks
FromSent OnAttachments
Phillip B OldhamMar 25, 2008 2:43 am 
Reinis RozitisMar 25, 2008 4:30 am 
Phillip B OldhamMar 25, 2008 4:47 am 
Yordan GeorgievMar 25, 2008 1:01 pm 
Phillip B OldhamMar 26, 2008 1:12 am 
ThomasMar 26, 2008 2:43 am 
Phillip B OldhamMar 26, 2008 3:00 am 
ThomasMar 26, 2008 3:08 am 
Corey DonohoeMar 26, 2008 7:18 am 
Yordan GeorgievMar 26, 2008 7:27 am 
Rob SchultzMar 26, 2008 12:14 pm 
Phillip B OldhamMar 28, 2008 2:36 am 
ThomasMar 29, 2008 1:41 pm 
Reinis RozitisMar 30, 2008 5:56 pm 
ThomasMar 31, 2008 4:41 am 
Phillip B OldhamMar 31, 2008 4:54 am 
Grzegorz NosekMar 31, 2008 5:06 am 
Phillip B OldhamMar 31, 2008 5:27 am 
Grzegorz NosekMar 31, 2008 5:40 am 
Phillip B OldhamMar 31, 2008 5:46 am 
Grzegorz NosekMar 31, 2008 6:33 am 
Phillip B OldhamMar 31, 2008 6:44 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: php-fastcgi and memory leaksActions...
From:Thomas (iamk@public.gmane.org)
Date:Mar 26, 2008 2:43:36 am
List:ru.sysoev.nginx

Hi Phillip,

Do you mind sharing your monitrc section concerning the monitoring of the spawn-fcgi process? I am currently unable to do so. This way I could hammer my php apps with httperf and see if I also have this memory leaks problem.

On Wed, Mar 26, 2008 at 9:12 AM, Phillip B Oldham <phi@theactivitypeople.co.uk> wrote:

I'm using spawn-fcgi, from the lighttpd project. It seemed the easiest way to manage the php instances. Is there a better way to spawn php instances for nginx?

Yordan Georgiev wrote: Hello Phillip,

How to create you are fastcgi gataway?

-- Please excuse my bad english...

С уважение, Й. Георгиев.

WEB: http://gigavolt-bg.net/ Blog: http://live.gigavolt-bg.net/

--

Phillip B Oldham The Activity People phi@theactivitypeople.co.uk ________________________________

Policies

This e-mail and its attachments are intended for the above named recipient(s) only and may be confidential. If they have come to you in error, please reply to this e-mail and highlight the error. No action should be taken regarding content, nor must you copy or show them to anyone.

This e-mail has been created in the knowledge that Internet e-mail is not a 100% secure communications medium, and we have taken steps to ensure that this e-mail and attachments are free from any virus. We must advise that in keeping with good computing practice the recipient should ensure they are completely virus free, and that you understand and observe the lack of security when e-mailing us. ________________________________