From owner-freebsd-current Sun Aug 2 17:56:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06057 for freebsd-current-outgoing; Sun, 2 Aug 1998 17:56:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (haiti-77.ppp.hooked.net [206.169.228.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06048 for ; Sun, 2 Aug 1998 17:56:44 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.8) with SMTP id RAA00535; Sun, 2 Aug 1998 17:57:52 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sun, 2 Aug 1998 17:57:51 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Garrett Wollman cc: current Subject: Re: listen() and SOMAXCONN? In-Reply-To: <199808030051.UAA21748@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 2 Aug 1998, Garrett Wollman wrote: > < said: > > > defined in sys/socket.h. A quick check of the man page informs me that I > > should use the MIB kern.somaxconn. Well, I checked the header files, and > > SOMAXCONN is defined to 128 in sys/socket.h, and there is no > > kern.somaxconn MIB. Any thoughts? > > Under FreeBSD, you should use -1. The MIB variable is in the kern.ipc > subtree. For portability, you should be prepared to use SOMAXCONN on > other systems. (It's easy to imagine an autoconf test which would > determine whether -1 works or not, or you could just do it at run > time.) Ahh, quite nifty indeed. Thanks :) - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message