Skip Menu |
Report information
Id: 3262
Status: resolved
Priority: 0/
Queue: perl5

Owner: Nobody
Requestors: mitchell [at] pienetworks.com
Cc:
AdminCc:

Operating System: generic
PatchStatus: (no value)
Severity: low
Type: notabug
Perl Version: (no value)
Fixed In: (no value)



Date: Fri, 19 May 2000 11:08:53 -0400
Subject: Bug/Inconsistency in POP3.pm (libnet) with perl5.6.0
To: gbarr [...] pobox.com, perlbug [...] perl.com
From: Mitchell Brandsma <mitchell [...] pienetworks.com>
Hi, I have spent a couple of hours tearing my hair out over this, and found an easy work-around... this happened since grabbing perl5.6 and libnet1.0703. The problem: perl code using Net::POP3.pm was failing to connect to the localhost. Examining the logs showed it never tried - running with debug showed the constructor always returned undef. Grabbing the smtp port works fine, as does sunrpc and a couple of other ports. It turns out that the POP3 module attempts to get the port for "pop3" service, where this basically standard Linux 2.2.13 (Redhat 6.1 with a kernel upgrade) has "pop-3" entries in the /etc/services file instead. Somehow perl 5.005 worked as it was. ARRRGGGH!!! AFTER the light-bulb appeared over my head, I put pop3 entries in the services file and all is well. Is it possible to get libnet to check for alternatives like this? Or is this really a bug in perl's getservbyname? Keep up the excellent work guys, - Mitchell Brandsma (mitchell@pienetworks.com) E-mail service provided by pieLINK (/)
Date: Fri, 19 May 2000 08:18:06 +0100
From: Graham Barr <gbarr [...] pobox.com>
To: Mitchell Brandsma <mitchell [...] pienetworks.com>
Cc: perlbug [...] perl.com
Subject: Re: Bug/Inconsistency in POP3.pm (libnet) with perl5.6.0
Download (untitled) / with headers
text/plain 1.2k
THis is a bug in the version of IO::Socket that was included in 5.6, I belive it is to be fixed in 5.6.1 Graham. On Fri, May 19, 2000 at 11:08:53AM -0400, Mitchell Brandsma wrote: Show quoted text
> Hi, > > I have spent a couple of hours tearing my hair out over this, and found an easy work-around... this happened since grabbing perl5.6 and libnet1.0703. > > The problem: perl code using Net::POP3.pm was failing to connect to the localhost. Examining the logs showed it never tried - running with debug showed the constructor always returned undef. Grabbing the smtp port works fine, as does sunrpc and a couple of other ports. It turns out that the POP3 module attempts to get the port for "pop3" service, where this basically standard Linux 2.2.13 (Redhat 6.1 with a kernel upgrade) has "pop-3" entries in the /etc/services file instead. Somehow perl 5.005 worked as it was. ARRRGGGH!!! > > AFTER the light-bulb appeared over my head, I put pop3 entries in the services file and all is well. Is it possible to get libnet to check for alternatives like this? Or is this really a bug in perl's getservbyname? > > Keep up the excellent work guys, > - Mitchell Brandsma (mitchell@pienetworks.com) > E-mail service provided by pieLINK (/)
Date: Wed, 07 Jun 2000 15:52:49 +0200
From: Richard Foley <Richard.Foley [...] m.dasa.de>
Subject: [ID 20000518.009] Bug/Inconsistency in POP3.pm (libnet) with perl5.6.0
To: perl5-porters [...] perl.org
Hi, I have spent a couple of hours tearing my hair out over this, and found an easy work-around... this happened since grabbing perl5.6 and libnet1.0703. The problem: perl code using Net::POP3.pm was failing to connect to the localhost. Examining the logs showed it never tried - running with debug showed the constructor always returned undef. Grabbing the smtp port works fine, as does sunrpc and a couple of other ports. It turns out that the POP3 module attempts to get the port for "pop3" service, where this basically standard Linux 2.2.13 (Redhat 6.1 with a kernel upgrade) has "pop-3" entries in the /etc/services file instead. Somehow perl 5.005 worked as it was. ARRRGGGH!!! AFTER the light-bulb appeared over my head, I put pop3 entries in the services file and all is well. Is it possible to get libnet to check for alternatives like this? Or is this really a bug in perl's getservbyname? Keep up the excellent work guys, - Mitchell Brandsma (mitchell@pienetworks.com) E-mail service provided by pieLINK (/)
To: Mitchell Brandsma <mitchell [...] pienetworks.com>
Cc: perl5-porters [...] perl.org
Subject: Re: [ID 20000518.009] Bug/Inconsistency in POP3.pm (libnet) with perl5.6.0
Date: Wed, 07 Jun 2000 10:33:33 -0700
From: Gurusamy Sarathy <gsar [...] ActiveState.com>
Download (untitled) / with headers
text/plain 1.1k
On Wed, 07 Jun 2000 15:52:49 +0200, Richard Foley wrote: Show quoted text
>I have spent a couple of hours tearing my hair out over this, and found an >easy work-around... this happened since grabbing perl5.6 and libnet1.0703. > >The problem: perl code using Net::POP3.pm was failing to connect to the >localhost. Examining the logs showed it never tried - running with debug >showed the constructor always returned undef. Grabbing the smtp port works >fine, as does sunrpc and a couple of other ports. It turns out that the POP3 >module attempts to get the port for "pop3" service, where this basically >standard Linux 2.2.13 (Redhat 6.1 with a kernel upgrade) has "pop-3" entries >in the /etc/services file instead. Somehow perl 5.005 worked as it was. >ARRRGGGH!!! > >AFTER the light-bulb appeared over my head, I put pop3 entries in the services >file and all is well. Is it possible to get libnet to check for alternatives >like this? Or is this really a bug in perl's getservbyname?
Yes, it is a bug in the new IO::Socket. Thanks for reporting it. You'll find a patch in the perl5-porters archives. (See perlhack.pod for where that is.) Sarathy gsar@ActiveState.com
according to the bug dialogue, its fixed in 5.6.1


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

For issues related to this RT instance (aka "perlbug"), please contact perlbug-admin at perl.org