Date: Tue, 18 Jan 2005 10:52:53 +0100 (CET) From: Rudolf Cejka <cejkar@fit.vutbr.cz> To: FreeBSD-gnats-submit@FreeBSD.org Subject: docs/76399: [PATCH] sendto(2) is missing possible error EISCONN Message-ID: <200501180952.j0I9qr8k045665@kazi.fit.vutbr.cz> Resent-Message-ID: <200501181000.j0IA0lYt077742@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 76399 >Category: docs >Synopsis: [PATCH] sendto(2) is missing possible error EISCONN >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Tue Jan 18 10:00:46 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Rudolf Cejka >Release: FreeBSD 5.3-STABLE i386 >Organization: FIT, Brno University of Technology, Czech Republic >Environment: >Description: SUSv3 says for sendto(): [EISCONN] A destination address was specified and the socket is already connected. This error may or may not be returned for connection mode sockets. FreeBSD does it in the first way (whereas Linux in the second) and the error in case of non-NULL destination address is reported. However, the manual page is quiet about it: --- lib/libc/sys/send.2.orig Tue Jan 18 10:38:19 2005 +++ lib/libc/sys/send.2 Tue Jan 18 10:39:14 2005 @@ -186,6 +186,8 @@ from the last message sent. This typically means that the receiver is not listening on the remote port. +.It Bq Er EISCONN +A destination address was specified and the socket is already connected. .It Bq Er EHOSTDOWN The remote host was down. .It Bq Er ENETDOWN >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200501180952.j0I9qr8k045665>