|The stupid question is the question not asked|
Re: io::socket::inet change from 5.8.4 to 5.8.6?by smackdab (Pilgrim)
|on Apr 17, 2005 at 03:14 UTC||Need Help??|
looks like ICMP and win32 isn't too popular...as it looks like a bug from a recent addition to 5.8.6:
I posted to p5p so they could fix it correctly...all I could do was a hack ;-) to get it working for me...
If anyone else reads this, don't call "open_ifs_socket()" replace it with "socket()". IFS won't work, but I didn't care
Looks like this new addition had a side-effect:
Change 23317: Integrate:
Fri, 10 Sep 2004 08:00:21 -0700
(here is the change: Change 23573: Create perl587delta.pod) PERL_ALLOW_NON_IFS_LSP (specific to the Win32 port) Set to 1 to allow the use of non-IFS compatible LSP's. Perl normally searches for an IFS-compatible LSP because this is required for its emulation of Windows sockets as real filehandles. However, this may cause problems if you have a firewall such as McAfee Guardian which requires all applications to use its LSP which is not IFS-compatible, because clearly Perl will normally avoid using such an LSP. Setting this environment variable to 1 means that Perl will simply use the first suitable LSP enumerated in the catalog, which keeps McAfee Guardian happy (and in that particular case Perl still works too because McAfee Guardian's LSP actually plays some other games which allow applications requiring IFS compatibility to work).