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 try to reproduce with Catalyst-Runtime-5.8000_06. It has a fix >> related to spawning external processes from the dev server. > > $ PERL5LIB=$HOME/cur_cat script/pipe_server.pl > 5.8000_06 > You can connect to your server at http://bumby2:3000 > about to read from handle > hello > > Same problem. > >
is it possible this is related to how Cat can mess with STDOUT and STDIN? I have these lines in SVN::Class: # this trick cribbed from mst's Catalyst::Controller::WrapCGI # we alias STDIN and STDOUT since Catalyst (and presumaly other code) # might be messing with STDOUT or STDIN open( *REAL_STDIN, "<&=" . fileno(*STDIN) ); open( *REAL_STDOUT, ">>&=" . fileno(*STDOUT) ); -- Peter Karman . pe...@peknet.com . http://peknet.com/ _______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/