From owner-freebsd-hackers  Tue Feb 20 10:44:34 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from smtp.nettoll.com (matrix.nettoll.net [212.155.143.61])
	by hub.freebsd.org (Postfix) with ESMTP id 3703337B4EC
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 20 Feb 2001 10:44:31 -0800 (PST)
	(envelope-from usebsd@free.fr)
Received: by smtp.nettoll.com; Tue, 20 Feb 2001 19:41:52 +0100 (MET)
Message-Id: <4.3.0.20010220193733.0576cd40@pop.free.fr>
X-Sender: usebsd@pop.free.fr
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Tue, 20 Feb 2001 19:43:53 +0100
To: Drew Eckhardt <drew@PoohSticks.ORG>
From: mouss <usebsd@free.fr>
Subject: Re: postfix: No buffer space available 
Cc: Len Conrad <LConrad@Go2France.com>, freebsd-hackers@FreeBSD.ORG
In-Reply-To: <200102201834.f1KIYMn29117@chopper.Poohsticks.ORG>
References: <Your message of "Tue, 20 Feb 2001 19:24:22 +0100." <4.3.0.20010220192222.04fd4100@pop.free.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 11:34 20/02/01 -0700, Drew Eckhardt wrote:
>These control the default socket buffer size.  Assuming postfix
>is not setting the appropriate socket options, when they are increased
>space will run out with even fewer connections.  If they are decreased
>such that they are less than the bandwidth delay product, you will have
>TCP/IP performance problems.
>
>The original poster needs to play with some of the kern.ipc values
>instead, most notably kern.ipc.maxsockbuf.

You're right.
a quick check shows that ENOBUFS may be caused by too many things,
including mbuf allocation failures, and even the network interface queue
has its "word"...

cheers,
mouss


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message