From owner-freebsd-security Wed Jan 24 7:18:48 2001 Delivered-To: freebsd-security@freebsd.org Received: from neo.spbnit.ru (mail.spbnit.ru [212.48.192.115]) by hub.freebsd.org (Postfix) with ESMTP id 555D037B698 for ; Wed, 24 Jan 2001 07:18:24 -0800 (PST) Received: from localhost.localdomain (ppp-195.pool-113.spbnit.ru [212.48.192.195]) by neo.spbnit.ru (8.9.3+mPOP/8.9.3) with SMTP id SAA39725; Wed, 24 Jan 2001 18:18:17 +0300 (MSK) From: "Mr. Blackman" Reply-To: blackman@blackman.ru To: "Sean O'Connell" Subject: Re: DoS: socket: No buffer space available Date: Wed, 24 Jan 2001 18:07:57 +0300 X-Mailer: KMail [version 1.0.29] Content-Type: text/plain References: <01012417332701.31962@localhost.localdomain> <20010124093824.C64654@stat.Duke.EDU> In-Reply-To: <20010124093824.C64654@stat.Duke.EDU> Cc: freebsd-security@freebsd.org MIME-Version: 1.0 Message-Id: <01012418184202.31962@localhost.localdomain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org options NMBCLUSTERS=32768 options NSFBUFS=32768 ...always- this is the first thing, that I made on new servers. netstat -m - 30% used or so... I would like to know all possible reasons of socket: no buffer space available (for example: $sudo bash: socket: no buffer space available) > > I would guess MBUF exhaustion as the cause. Look at > > netstat -m > > /sys/i386/conf/LINT has some tuning examples. I think this works > under RELENG_3 > > options NMBCLUSTERS=8192 > > (or bigger). You can also up the # of maxusers to 128 or something > as this will resize most of the kernel tables. I fear a reboot may > be the only short term fix. > > S > -- > Sean O'Connell Email: sean@stat.Duke.EDU > Institute of Statistics and Decision Sciences Phone: (919) 684-5419 > Duke University Fax: (919) 684-8594 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message