Re: ECONNREFUSED in recvfrom ?

Andi Kleen (ak@muc.de)
13 Oct 1998 21:32:21 +0200

In article <m0zT6Hl-0007U9C@the-village.bc.nu>,
alan@lxorguk.ukuu.org.uk (Alan Cox) writes:
>> refused wasn't an option. On the glibc info pages, "recvfrom" doesn't
>> have documented return codes and "recv" doesn't offer connection refused
>> as an error code. Either libc5 and glibc documentation is broken or the
>> kernel is returning an invalid error code - what does POSIX have to say?

> POSIX doesn't have to say. 1003.1g is still unfinished and has fundamental
> design flaws that even though I have pointed them out to the listed contacts
> have not been resolved as far as I know. In paticular the bind() function
> is assumed to be atomic. Name binding is not atomic for all protocols.

> The man pages are a valid point. Andi Kleen is working on an update for
> these including notes on all the new 2.1.x features, I'm sure he would
> appreciate help.

ECONNREFUSED is documented in my latest version of udp(4) and ip(4). I
would welcome reviewers (I'm no native English speaker) and contributions/
bug reports.

A snapshot (not finished) is at ftp://ftp.muc.de/people/ak/netman-131098.tgz

-Andi

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/