From owner-freebsd-hackers  Thu Dec 26 06:02:11 1996
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id GAA20898
          for hackers-outgoing; Thu, 26 Dec 1996 06:02:11 -0800 (PST)
Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id GAA20893
          for <hackers@FreeBSD.ORG>; Thu, 26 Dec 1996 06:02:08 -0800 (PST)
Received: by kaori.communique.net with Microsoft Exchange (IMC 4.0.837.3)
	id <01BBF302.C20B1150@kaori.communique.net>; Thu, 26 Dec 1996 07:59:45 -0600
Message-ID: <c=US%a=_%p=Communique._Inc.%l=KAORI-961226135944Z-3229@kaori.communique.net>
From: Raul Zighelboim <mango@staff.communique.net>
To: "'proff@suburbia.net'" <proff@suburbia.net>
Cc: "'hackers@FreeBSD.ORG'" <hackers@FreeBSD.ORG>
Subject: RE: Help 'no buffer available'!!
Date: Thu, 26 Dec 1996 07:59:44 -0600
X-Mailer:  Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



As I have seen the server die no long after this messages pop up,
I am glad I am receiving them :-) or :-(
>> 
>> ----kiyoko:/var/log# ping akira
>> PING akira.communique.net (204.27.65.10): 56 data bytes
>> 64 bytes from 204.27.65.10: icmp_seq=0 ttl=255 time=0.867 ms
>> ping: sendto: No buffer space available
>> ping: wrote akira.communique.net 64 chars, ret=-1
>> ping: sendto: No buffer space available
>
>I often get this as well. What is the philosophy in having
>sendto() et al return an error, rather than block until
>buffer space is available?
>
>