| Subject: | Won't work on cygwin (perhaps solved) |
| Date: | Wed, 17 May 2006 16:02:45 -0500 |
| To: | bug-poe-component-client-ping [...] rt.cpan.org |
| From: | Michael Costello <fraterm [...] ideologies.org> |
I had some trouble getting my (recently installed) cygwin distribution
to use POE::Component::Client::Ping while writing a super-application
bent on world domination, luckily I was able to resolve it by altering
the module somewhat.
The problem lies in the assumption that the "root" user exists on
cygwin, it does not necessarily exist, though the userid you operate
under may have enough authority to abuse packets appropriately P-C-C-P
decides to croak (see line 52 of POE/Component/Client/Ping.pm ) unless
you are running on VMS, simply changing this line (52) from:
$> and ($^O ne "VMS") and not defined $params{Socket}
to:
$> and ( $^O ne ("cygwin" or "VMS") ) and not defined
$params{Socket}
solves the issue of it immediately denying a spawn, it seems to work for
me currently with this adjusted only changing Ping.pm and 'use lib' ing
in order to point to my version of the module.
I'd love my pony made of a million dollars now, I heard 'dngor' was
giving those out.