From owner-freebsd-hackers Wed Dec 25 22:48:27 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA10342 for hackers-outgoing; Wed, 25 Dec 1996 22:48:27 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA10337 for ; Wed, 25 Dec 1996 22:48:25 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id WAA02511 for ; Wed, 25 Dec 1996 22:49:10 -0800 (PST) Received: (qmail 5748 invoked by uid 110); 26 Dec 1996 06:48:14 -0000 Message-ID: <19961226064814.5747.qmail@suburbia.net> Subject: Re: Help 'no buffer available'!! In-Reply-To: from Raul Zighelboim at "Dec 25, 96 07:52:28 pm" To: mango@staff.communique.net (Raul Zighelboim) Date: Thu, 26 Dec 1996 17:48:14 +1100 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] 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 > My poor news server is sick..... > > ----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?