Catalyst, FastCGI and fork

Hello,

I'm currently working on a Catalyst project using FastCGI. The problem is, I can't figure out how to fork correctly within the application. A simple fork call leaves me with fastcgi zombie processes.

I've read the FastCGI FAQ (http://www.fastcgi.com/docs/faq.html#Perlfork ) and it seems like thats what I need. But I can't find a way to get the FCGI::Request object.

Comment on Catalyst, FastCGI and fork
Re: Catalyst, FastCGI and fork by Anonymous Monk on Feb 11, 2013 at 03:44 UTC
I've read the FastCGI FAQ (http://www.fastcgi.com/docs/faq.html#Perlfork ) and it seems like thats what I need. But I can't find a way to get the FCGI::Request object. IMHO, you don't really need that (if this old post http://stackoverflow.com/questions/2592157/whats-the-proper-way-to-fork-in-fastcgi is any indication of what you're doing ) Read Highlander: one instance at a time (Oct 00), Watching long processes through CGI (Aug 02), Proc::Background So in your runmode parent, you brand / fork, and return a redirect response in the child you disassociate completely, you don't return responses, you do the work, and you update the session/cache -- this should eliminate zombies	[reply]
Re: Catalyst, FastCGI and fork by Anonymous Monk on Feb 11, 2013 at 13:09 UTC
Better yet hand the request (e.g. by another FastCGI-protocol link... why not?) to a true offline-service process. "POE" would do as a basis in a pinch. Let the online web-user monitor the progress of the batch job, and to retrieve the results when finished.	[reply]


Your skill will accomplish what the force of many cannot
	PerlMonks

Catalyst, FastCGI and fork

How many continents have you visited?