From owner-freebsd-questions  Tue Feb 25 07:31:09 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA27329
          for questions-outgoing; Tue, 25 Feb 1997 07:31:09 -0800 (PST)
Received: from silver.sms.fi (silver.sms.fi [194.111.122.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA27317
          for <freebsd-questions@FreeBSD.ORG>; Tue, 25 Feb 1997 07:30:57 -0800 (PST)
Received: (from pete@localhost) by silver.sms.fi (8.8.5/8.7.3) id RAA02889; Tue, 25 Feb 1997 17:30:32 +0200 (EET)
Date: Tue, 25 Feb 1997 17:30:32 +0200 (EET)
Message-Id: <199702251530.RAA02889@silver.sms.fi>
From: Petri Helenius <pete@sms.fi>
To: Doug White <dwhite@resnet.uoregon.edu>
Cc: freebsd-questions@FreeBSD.ORG
Subject: Re: socket buffers
In-Reply-To: <Pine.BSI.3.94.970224231723.4530U-100000@localhost>
References: <199702222146.XAA00595@silver.sms.fi>
	<Pine.BSI.3.94.970224231723.4530U-100000@localhost>
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Doug White writes:
 > 
 > Run 'netstat -m' to get the memory info and post that.
 > 
 > You may need to increase your mbufs.
 > 
As a helpful gentleman already instructed me of the setsockopt call
which is neccessary to increase the allocated buffer size and I
figured out the neccessary sysctl to increase myself (to up the max
allowed). I did run out of mbufs in the process though :-) And the
system paniced.

Pete