From owner-freebsd-bugs Fri Sep 4 04:10:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA09379 for freebsd-bugs-outgoing; Fri, 4 Sep 1998 04:10:07 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA09368 for ; Fri, 4 Sep 1998 04:10:06 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id EAA05756; Fri, 4 Sep 1998 04:10:00 -0700 (PDT) Date: Fri, 4 Sep 1998 04:10:00 -0700 (PDT) Message-Id: <199809041110.EAA05756@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: Bruce Evans Subject: Re: kern/7831: Inclusion of kernel variable SOMAXCONN as a configurable option Reply-To: Bruce Evans Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/7831; it has been noted by GNATS. From: Bruce Evans To: freebsd-gnats-submit@FreeBSD.ORG, Roy.Nicholl@ASGtechnologies.com Cc: Subject: Re: kern/7831: Inclusion of kernel variable SOMAXCONN as a configurable option Date: Fri, 4 Sep 1998 21:06:22 +1000 >>Description: >In certain situations [i.e. high volume proxy server] it is necessary to adjust the value of >SOMAXCONN upward from its default of 128. Use the kern.ipc.somaxconn variable. SOMAXCONN shouldn't even be visible (since it it just misleading if someone has changed kern.ipc.somaxconn). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message