This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH][BZ #14719] Return EAI_SYSTEM from getaddrinfo if we run out of fds
- From: Siddhesh Poyarekar <siddhesh dot poyarekar at gmail dot com>
- To: GNU C Library <libc-alpha at sourceware dot org>
- Date: Tue, 2 Apr 2013 12:48:44 +0530
- Subject: Re: [PATCH][BZ #14719] Return EAI_SYSTEM from getaddrinfo if we run out of fds
- References: <20121023171835 dot 09f1b085 at spoyarek> <20130325125824 dot GA11387 at altlinux dot org> <CAAHN_R1OWczQtSFVHK3DVdqBg4+qKivxMoN_6gjfxxGiyzYO8A at mail dot gmail dot com> <20130401171156 dot GB9522 at altlinux dot org>
On 1 April 2013 22:41, Dmitry V. Levin <ldv@altlinux.org> wrote:
> $ ip a
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> $ ip r
OK, so bring down network *and* unload networking modules.
I got an EAI_SYSTEM when I linked against a stale build of last
month's code (March 26th to be specific). I did a clean build there
and it has been giving me EAI_NONAME ever since. So I'm still not
able to reproduce the problem the way you are. Also, are you sure
that the behaviour before the patch was EAI_AGAIN and not EAI_NONAME?
I've been getting EAI_NONAME for everything since 2.15 and it seems
like the right thing to do to me.
Siddhesh
--
http://siddhesh.in