Re: FastCGI Expert Sought
Ross Richey <[email protected]>
| Newsgroups | gmane.comp.web.fastcgi.devel |
|---|---|
| Message-ID | <[email protected]> |
Thanks for all the responses. Some more details: It may be that this is more of a conceptual problem than a technical problem. Several people have suggested that PERL is the problem. And indeed in a sense it is. It's really hard to keep PERL from leaking memory, so hard it's not worth even trying. This wouldn't be a problem if, after a certain number of requests, we could just nicely kill the old FastCGI process and respawn a new one. Instead we get processes which are defunct and Lighttpd will eventually run out of live FastCGI processes to use and then it will no longer be able to serve those requests. So yes this might be something which needs to be handled at the Lighttpd level. But before we do that I just want to ask the conceptual question: Is there some method of nicely killing and respawning a FastCGI process? The reason I asked for an expert and offered money is that we're fully expecting that we might have to get someone to actually add that functionality to FastCGI, but obviously I'm open to other ideas on fixing the problem. Ross On Thu, Jul 16, 2009 at 3:30 PM, Perrin Harkins <[email protected]> wrote: > If you haven't already, I'd suggest you ask on the Lighttpd list. > > - Perrin > _______________________________________________ FastCGI-developers mailing list FastCGI-developers-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org http://mailman.pins.net/mailman/listinfo.cgi/fastcgi-developers