[EMAIL PROTECTED] (Wes Peters) writes:
> [ENOBUFS] Insufficient system buffer space exists to complete the op-
> eration.
Do you know what kind of circumstances that error *really* occurs
under?
If it happened with files, that would be a bug and should be fixed.
The call is supposed to block to wait for writes to be possible. This
applies to stream sockets in most cases, as well. Based on a quick
look at the code, out-of-band TCP data seems to be the only case where
ENOBUFS might be returned for streams, and that obviously doesn't
apply to write/writev.
As I mentioned to Nik in private mail, for datagram sockets, the
description in send(2) more or less applies. Programs should
generally use send rather than write for such objects, anyhow.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
