From owner-freebsd-net Mon Feb 28 8: 9:48 2000 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id E1BCC37B8B0; Mon, 28 Feb 2000 08:09:42 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA52053; Mon, 28 Feb 2000 11:09:41 -0500 (EST) (envelope-from wollman) Date: Mon, 28 Feb 2000 11:09:41 -0500 (EST) From: Garrett Wollman Message-Id: <200002281609.LAA52053@khavrinen.lcs.mit.edu> To: James FitzGibbon Cc: freebsd-questions@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: How to rememdy ENOBUFS return from socket(2) ? In-Reply-To: <20000228103711.B10570@targetnet.com> References: <20000228103711.B10570@targetnet.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > My question is: if the system is running out of space in this zone, should I > be tweaking kern.ipc.maxsockets using sysctl, or trying to hunt down > whatever errant process is sucking up the zone ? kern.ipc.maxsockets is read-only. You'll have to change it in your kernel configuration (or from the boot loader) if that's really the problem. maxsockets should be 24616 (==maxfiles) according to the config snippet you posted. If your machine actually has 24,000 active sockets, perhaps there's something wrong with it. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message