-hackers,
Could someone who knows write/writev(2) take a quick look at docs/10512.
In essence, writev(2) can fail with ENOBUFS if (and I quote from the PR)
if you "exhaust writev'able buffer space". This doesn't mean a great
deal to me, and I'm hoping one of you can take a look at come up with a
phrasing suitable for a man page.
Cheers,
N
--
[intentional self-reference] can be easily accommodated using a blessed,
non-self-referential dummy head-node whose own object destructor severs
the links.
-- Tom Christiansen in <[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
