On Wed, Feb 04, 2009 at 10:25:15PM -0800, Bill Moseley wrote:
I have a module that uses IO::Pipe and when I run it under the
Catalyst server the pipe doesn't work (see below).
Please try to reproduce with Catalyst-Runtime-5.8000_06. It has a fix
related to spawning external processes from the
2009/2/5 Florian Ragwitz r...@debian.org
On Wed, Feb 04, 2009 at 10:25:15PM -0800, Bill Moseley wrote:
I have a module that uses IO::Pipe and when I run it under the
Catalyst server the pipe doesn't work (see below).
Please try to reproduce with Catalyst-Runtime-5.8000_06. It has a fix
On Thu, Feb 05, 2009 at 12:51:18PM +, Peter Edwards wrote:
Was that the change to the catching of signal SIGCHLD ?
Exactly.
--
BOFH excuse #66:
bit bucket overflow
signature.asc
Description: Digital signature
___
List:
On Thu, Feb 05, 2009 at 01:23:03PM +0100, Florian Ragwitz wrote:
On Wed, Feb 04, 2009 at 10:25:15PM -0800, Bill Moseley wrote:
I have a module that uses IO::Pipe and when I run it under the
Catalyst server the pipe doesn't work (see below).
Please try to reproduce with
On Thu, Feb 05, 2009 at 07:10:07AM -0800, Bill Moseley wrote:
Same problem.
Would you mind preparing a testcase for this?
TestApp::Controller::Fork / t/live_fork.t already has similar tests. You
can run them against the dev server using t/optional_http-server.t.
--
BOFH excuse #86:
Runt
Bill Moseley wrote on 02/05/2009 09:10 AM:
On Thu, Feb 05, 2009 at 01:23:03PM +0100, Florian Ragwitz wrote:
On Wed, Feb 04, 2009 at 10:25:15PM -0800, Bill Moseley wrote:
I have a module that uses IO::Pipe and when I run it under the
Catalyst server the pipe doesn't work (see below).
Please
On Thu, Feb 05, 2009 at 04:28:57PM +0100, Florian Ragwitz wrote:
On Thu, Feb 05, 2009 at 07:10:07AM -0800, Bill Moseley wrote:
Same problem.
Would you mind preparing a testcase for this?
I can try. See attached diff against svn 9215.
$ prove -vl t/live_fork.t
t/live_fork
1..15
I have a module that uses IO::Pipe and when I run it under the
Catalyst server the pipe doesn't work (see below).
Anyone using IO::Pipe in an application? Even if not, any idea
what's happening here? Is the Cat server selecting this handle
somehow?
If I run the application with mod_perl the