Bug/Inconsistency in POP3.pm (libnet) with perl5.6.0

[p5pRT]

Migrated from rt.perl.org#3262 (status was 'resolved')

Searchable as RT3262$

[p5pRT]

From 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 (/)

[p5pRT]

From @gbarr

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​:

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 (/)

[p5pRT]

From [Unknown Contact. See original ticket]

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 (/)

[p5pRT]

From @gsar

On Wed, 07 Jun 2000 15​:52​:49 +0200, Richard Foley wrote​:

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

[p5pRT]

From @iabyn

according to the bug dialogue, its fixed in 5.6.1

[p5pRT]

@iabyn - Status changed from 'open' to 'resolved'