On May 24, 2007, at 9:40 AM, Jon Schutz wrote:
On Thu, 2007-05-24 at 08:13 -0400, Andy Grundman wrote:
No, I hadn't set CATALYST_POE_MAX_PROC as I'm happy with forking on-
demand in this app. However, I just tried it now, and it made no
difference.
The POE engine does not fork at all unless you have set this
variable, so I'm confused how you are getting child processes without
it? There is no fork-on-demand in the POE engine, that's only a
feature of the default HTTP engine.
OK, fair call, fork-on-demand was my assumption... that explains why I
didn't see it mentioned in the perldoc. And, I've misled you; I had
tucked away max_proc = 3 in an options hash that I'd forgotten about.
So yes, I am using preforking. Turning on debugging, it preforks two
processes as expected.
Now, some good news (at least from my perspective). I had been
terminating the child with a SIGTERM; I've just tried SIGINT instead,
and that seems to clean up nicely.
Aha, I forgot to put in a SIGTERM handler, I'll do this and it should
fix the issue. :)
_______________________________________________
List: [email protected]
Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
