OK, now I've dug around. The real problem is
make_socket failed: peer not server at blib/lib/POE/Pipe.pm line 153.
See patch below that creates better warnings for debuging.
Oh, and the code to choose what kind of socket to open in
POE::Pipe::OneWay is, uh, interesting!
On 02-Aug-2001 [EMAIL PROTECTED] wrote:
> However :
>
> $ perl t/22_wheel_run.t
>
> Works perfectly... :/
I was using an older version of POE. perl -Iblib/lib t/22_wheel_run.t
didn't work.
-Philip
--- POE/Pipe/OneWay.pm 2001/08/01 02:00:48 1.6
+++ POE/Pipe/OneWay.pm 2001/08/02 05:44:23
@@ -54,6 +54,8 @@
# someone might want to use the pipe class elsewhere.
select((select($b_write), $| = 1)[0]);
return($a_read, $b_write);
+ } elsif(DEBUG) {
+ warn "pipe failed: $@";
}
}
@@ -86,6 +88,8 @@
# might want to use the pipe class elsewhere.
select((select($b_write), $| = 1)[0]);
return($a_read, $b_write);
+ } elsif(DEBUG) {
+ warn "socketpair failed: $@";
}
}
@@ -126,6 +130,7 @@
# Sockets failed. Don't dry them again.
else {
+ DEBUG and warn "make_socket failed: $@";
$can_run_socket = 0;
}
}