Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 20768 invoked by uid 6000); 24 May 1998 22:45:05 -0000 Received: (qmail 20761 invoked from network); 24 May 1998 22:45:04 -0000 Received: from twinlark.arctic.org (204.62.130.91) by taz.hyperreal.org with SMTP; 24 May 1998 22:45:04 -0000 Received: (qmail 22585 invoked by uid 500); 24 May 1998 23:26:25 -0000 Date: Sun, 24 May 1998 16:26:25 -0700 (PDT) From: Dean Gaudet To: new-httpd@apache.org Subject: Re: SOMAXCONN and FreeBSD In-Reply-To: <199805222030.QAA13826@devsys.jaguNET.com> Message-ID: X-Comment: Visit http://www.arctic.org/~dgaudet/legal for information regarding copyright and disclaimer. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org You know, linux supports only a max of 128 without tweaking the kernel sources (they use an unsigned char, but do some arithmetic on it which could overflow if greater than 128, and ANSI doesn't guarantee the promotion to int that gcc does). Very few people change this on linux... I doubt it's actually even necessary these days. 5 is way to small, but 128 seems to be sufficient (even on fast lans with many clients). i.e. I don't think it's a biggie. Dean On Fri, 22 May 1998, Jim Jagielski wrote: > You know, I never really gave it much thought... I just took it > on faith that adding the options "SOMAXCONN=256" line actually > made the listen queue 256. I just ignored the warnings when > building a new kernel. And then I actually _looked_ at the > warnings... It's saying that the entry in sys/socket.h is > _overruling_ the initialization one! That is, it's not being > reset to 256, but instead the value of 256 is being changed > to 128 !! > -- > =========================================================================== > Jim Jagielski ||| jim@jaguNET.com ||| http://www.jaguNET.com/ > "That's no ordinary rabbit... that's the most foul, > cruel and bad-tempered rodent you ever laid eyes on" >