test_socket.py failure

[Marc Christiansen]

x2164 at mailcity.com wrote:
> Nick Coghlan <ncoghlan at iinet.net.au> wrote:
>> Hmm, when the second argument is omitted, the system call looks like:
>> 
>> getservbyname("daytime", NULL);
>> 
>> Based on "man getservbyname" on my Linux PC, that should give
>> the behaviour we 
>> want - any protocol will match.
>> 
>> However:
>> 
>> Linux 2.6.4-52-default (Suse 9.1)
>> Glibc 2.3.3
>> gcc   3.3.3
>> 
>> So it may be that your older platform doesn't have this
>> behaviour - I'd be very 
>> interested in what 'man getservbyname' has to say.
> 
>    Just took a look at the man page for getservbyname on this
>    system and it doesn't mention passing NULL as the second
>    argument.  The pertinents: ;-)
> 
>        Linux kernel 2.6.10
>        Glibc 2.2.5
>        gcc   2.95.3

Just to confuse the matter more, on my system the man page mentions
passing NULL as the second argument and it works. Alas:
SuSE 7.3
Kernel 2.4.29 (vanilla)
Glibc  2.2.4 (older than yours)
gcc    2.95.3

>    I'd say your probably right about there being a difference
>    in the behaviour of getservbyname between libc 2.2.5 and 
>    and libc-2.3.3 given the differences in man pages and 
>    observed return values. I'll try and compare the libcs'
>    getservbyname codes and let you know a little later in 
>    the day.
> 
>    I wonder if the developers wanted to tie the python source
>    code so closely to a glibc version and possibly gnu-libc
>    specific?

Perhaps SuSE did patch the glibc...

Saluton
  Marc