From owner-freebsd-current Thu Apr 12 17: 9:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 62A8637B423 for ; Thu, 12 Apr 2001 17:09:36 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f3D08nM61301; Thu, 12 Apr 2001 19:08:49 -0500 (CDT) (envelope-from jlemon) Date: Thu, 12 Apr 2001 19:08:49 -0500 (CDT) From: Jonathan Lemon Message-Id: <200104130008.f3D08nM61301@prism.flugsvamp.com> To: tlambert@primenet.com, current@freebsd.org Subject: Re: SOMAXCONN -- not tunable? X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >Here are patches to make SOMAXCONN tunable from the config files. > >Right now, it's not possible to override SOMAXCONN. sysctl -w kern.ipc.somxconn=1024 SOMAXCONN is just a compile time default, and yes it is not currently tunable at config time. Does it really have to be? Just stick it in /etc/sysctl.conf, and it gets set before most things are started in the system. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message