From owner-freebsd-hackers Fri Jul 30 9:35:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 5D8C5151AA for ; Fri, 30 Jul 1999 09:35:32 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA91238; Fri, 30 Jul 1999 09:34:46 -0700 (PDT) (envelope-from dillon) Date: Fri, 30 Jul 1999 09:34:46 -0700 (PDT) From: Matthew Dillon Message-Id: <199907301634.JAA91238@apollo.backplane.com> To: Ville-Pertti Keinonen Cc: wes@softweyr.com (Wes Peters), hackers@FreeBSD.ORG Subject: Re: Documenting writev(2) ENOBUFS error References: <19990728170119.A47890@kilt.nothing-going-on.org> <37A06B6B.B5BF74CF@softweyr.com> <86yafy5x55.fsf@not.demophon.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :wes@softweyr.com (Wes Peters) writes: : :> [ENOBUFS] Insufficient system buffer space exists to complete the op- :> eration. : :Do you know what kind of circumstances that error *really* occurs :under? : :If it happened with files, that would be a bug and should be fixed. :The call is supposed to block to wait for writes to be possible. This I am almost certain that this error can only occur when writing to sockets, and only then of the network mbuf pool is completely exhausted. UDP is probably the most vulernable. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message