> > ENOBUFS == ESYSADMINNEEDSTORAISENMBCLUSTERS
>
> Or perhaps ENOBUFS == E_SYSTEM_NEEDS_TO_RAISE_NMBCLUSTERS_ALL_ON_ITS_OWN?
it is not an NMBCLUSTERS problem, it is just the device queue
which is filling up, and this is a perfectly normal and desired
behaviour. One would just want that to be handled as in the
case of writes to a disk or the like -- i.e. wait until
the subsystem (in this case the network device) is ready.
For disks and TCP the synchronization is achieved through the socket
buffer and (presumably for disks as well, i am no expert on
filesystems) explicit acks on write ops.
For UDP sockets things are unfortunately a bit more complex
as there is no ack nor socket buffers. Plus there might be
around a ton of software which relies on the current
behaviour...
cheers
luigi
----------------------------------+-----------------------------------------
Luigi RIZZO, [EMAIL PROTECTED] . ACIRI/ICSI (on leave from Univ. di Pisa)
http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704
Phone: (510) 666 2927
----------------------------------+-----------------------------------------
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
