Differences between current version and predecessor to the previous major change of connect(2).
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 5 | Last edited on Sunday, February 23, 2003 2:26:05 pm | by PerryLorier | |
| Older page: | version 4 | Last edited on Tuesday, December 31, 2002 2:51:14 am | by PerryLorier | Revert |
@@ -35,12 +35,13 @@
;[EALREADY]: The socket is non-blocking and a previous connection attempt has not yet been completed.
;[EAGAIN]: No more free local ports or insufficient entries in the routing cache. For __PF_INET__ see the __net.ipv4.ip_local_port_range__ sysctl in ip(7) on how to increase the number of local ports.
;[EAFNOSUPPORT]: The passed address didn't have the correct address family in its ''sa_family'' field.
;[EACCES], [EPERM]: The user tried to connect to a broadcast address without having the socket broadcast flag enabled or the connection request failed because of a local firewall rule.
+;[EAFNOSUPPORT]: The address family is not supported by protocol
!!CONFORMING TO
-SVr4, 4.4BSD (the __connect__ function first appeared in BSD 4.2). SVr4 documents the additional general error codes [EADDRNOTAVAIL], [EINVAL], [EAFNOSUPPORT
], [EALREADY], [EINTR], [EPROTOTYPE], and [ENOSR]. It also documents many additional error conditions not described here.
+SVr4, 4.4BSD (the __connect__ function first appeared in BSD 4.2). SVr4 documents the additional general error codes [EADDRNOTAVAIL], [EINVAL], [EALREADY], [EINTR], [EPROTOTYPE], and [ENOSR]. It also documents many additional error conditions not described here.
!!NOTE
The third argument of __connect__ is in reality an int (and this is what BSD 4.* and libc4 and libc5 have). Some POSIX confusion resulted in the present socklen_t. The draft standard has not been adopted yet, but glibc2 already follows it and also has socklen_t. See also accept(2).
!!BUGS
