Differences between version 4 and predecessor to the previous major change of send(2).
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Monday, June 6, 2005 12:39:52 pm | by PerryLorier | Revert |
| Older page: | version 3 | Last edited on Tuesday, November 18, 2003 11:53:13 am | by JohnMcPherson | Revert |
@@ -52,11 +52,11 @@
;[ENOTSOCK]: The argument ''s'' is not a socket.
;[EFAULT]: An invalid user space address was specified for a parameter.
;[EMSGSIZE]: The socket requires that message be sent atomically, and the size of the message to be sent made this impossible.
;[EAGAIN] or [EWOULDBLOCK]: The socket is marked non-blocking and the requested operation would block.
-;[ENOBUFS]: The output queue for a network interface was full. This generally indicates that the interface has stopped sending, but may be caused by transient congestion. (This cannot occur in Linux, packets are just silently dropped when a device queue overflows.)
+;[ENOBUFS]: The output queue for a network interface was full. This generally indicates that the interface has stopped sending, but may be caused by transient congestion.
;[EINTR]: A signal occurred.
-;[ENOMEM}
: No memory available.
+;[ENOMEM]
: No memory available.
;[EINVAL]: Invalid argument passed.
;[EPIPE]: The local end has been shut down on a connection oriented socket. In this case the process will also receive a [SIGPIPE] unless __MSG_NOSIGNAL__ is set.
!!CONFORMING TO
