Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!ucsd!helios.ee.lbl.gov!ace.ee.lbl.gov!leres
From: leres@ace.ee.lbl.gov (Craig Leres)
Newsgroups: comp.bugs.4bsd
Subject: Re: A ping question and the infamous "sendto: No buffer space available" message
Message-ID: <4355@helios.ee.lbl.gov>
Date: 2 Dec 89 00:39:13 GMT
References: <1989Dec1.102932.15678@larouch.uucp>
Sender: usenet@helios.ee.lbl.gov
Reply-To: leres@helios.ee.lbl.gov (Craig Leres)
Organization: Yoyodyne Propulsion Systems
Lines: 27
X-Local-Date: 1 Dec 89 16:39:13 PST

Ralph Yozzo writes:
> Has anyone run into a situation where "ping'ing" a host
> gives a
>
> sendto:No buffer space available
>
> message.

Yeah, the usual cause of this is that a directly connected network is
hosed. There's a limit to the number of packets that you can queue to
the interface (usually 50) and once you reach this limit, you may not
queue any more and the No buffer space available error (ENOBUFS) is
returned.

> The only solution that I found is to reboot the machine.
> Needless to say, the administration people are not to
> thrilled with my constant rebooting.

I'll bet! Rebooting should be saved for the last resort. It's possible
that your hardware is broken or flakey. Sometimes you can reset it
without doing anything with software. Sometimes, you can reset the
hardware by ifconfig'ing the interface down and then back up. Of
course, if the problem is that your device driver is broken (maybe it's
doing something like dropping an interrupt) you're probably stuck with
rebooting until you fix the driver.

		Craig