Date: Tue, 20 Feb 2001 19:43:53 +0100 From: mouss <usebsd@free.fr> To: Drew Eckhardt <drew@PoohSticks.ORG> Cc: Len Conrad <LConrad@Go2France.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: postfix: No buffer space available Message-ID: <4.3.0.20010220193733.0576cd40@pop.free.fr> In-Reply-To: <200102201834.f1KIYMn29117@chopper.Poohsticks.ORG> References: <Your message of "Tue, 20 Feb 2001 19:24:22 %2B0100." <4.3.0.20010220192222.04fd4100@pop.free.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.3.0.20010220193733.0576cd40>