Date: Sun, 30 Nov 1997 10:57:00 -0700 (MST)
From: Marc Slemko <marcs@worldgate.com>
To: new-httpd@apache.org
Subject: Re: flock() question  (fwd)
In-Reply-To: <199711301747.JAA20130@hudsucker.gamespot.com>
Message-ID: <Pine.BSF.3.95q.971130105516.10673A-100000@valis.worldgate.com>
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

Do you have multiple Listen directives?  If so, you need accept locking.
Only trick is that USE_FLOCK_SERIALIZED_ACCEPT is broken in 1.2.  You
could try USE_FCNTL_SERIALIZED_ACCEPT instead; ie. replace the FLOCK in
the FreeBSD section of conf.h with FCNTL.

SAFE_UNSERIALIZED_ACCEPT won't do anything for 1.2.

On Sun, 30 Nov 1997, Random Junk wrote:

> Dean Gaudet writes:
> > +1 on SAFE_UNSERIALIZED_ACCEPT for freebsd 2.2+ then. 
> 
> i'm running freebsd 2.2.5/apache 1.2.4 and apache is getting stuck on
> a regular basis (i have a kill -HUP on an hourly cron to keep it
> happy).  the web traffic on that machine is extremely high (30
> connections/sec pretty much continuously, maybe even more now due to
> thanksgiving vacation).  top/vmstat shows a good amount of free ram
> and no swapping.
> 
> will SAFE_UNSERIALIZED_ACCEPT help?
> 
> could it also have anything to do with the listen queue on the
> machine?  (somaxconn is at 128).
> 
> i will experiment with both of those but i'd like to know as much as
> possible about potential impact before just blindly mucking about.
> 
> -- 
>     Jon Drukman       jsd@gamespot.com      SpotMedia Communications
> This calls for a very special blend of psychology and extreme violence.
>