> So this means the output queue on my net card is full, right? And I guess
> there is no easy solution... Oh well, I'll have to cope.

That's correct; the pipe is full, and you can't put any more bits in it.

Typically you run into this situation when your app is generating more 
data than can squirt out the hole in your network card, or the card is 
stalled for some reason.

Any app using socket I/O should be ready to handle ENOBUFS gracefully; it 
typically needs to pause and then retry the I/O.

> So, no solution, right? :(

If the card is stalled (possible), then you may have a driver problem.
But otherwise, it's not a "problem" except in the application.

... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to