Re: Re: Moving to PHP5.1 and Apache 2.2 next year, need help

From: Date: Fri, 12 Aug 2005 16:15:59 +0000
Subject: Re: Re: Moving to PHP5.1 and Apache 2.2 next year, need help
References: 1 2 3 4 5 6 7 8 9  Groups: php.internals 
Request: Send a blank email to internals+get-17874@lists.php.net to get a copy of this message 
On Aug 12, 2005, at 10:52 AM, steve roussey wrote:

On 8/12/05, Brian J. France <list@firehawksystems.com> wrote:

Really?  We just did a around of discussion/debugging on this at work
and I found that it uses ap_lingering_close which is like the
lingering_close function in 1.3.


:)

Yes, it does do ap_lingering_close, and it sets SO_LINGER. I have no
idea why they do both, I only assume they know what they are doing and
it works out for the best.


I see the code for SO_LINGER in apr_socket_opt_set, but I don't see any place in the server code that calls apr_socket_opt_set with APR_SO_LINGER.

Running gdb I see APR_SO_KEEPALIVE, APR_SO_REUSEADDR and APR_TCP_NODELAY passed to apr_socket_opt_set but not APR_SO_LINGER.

(This is based on the svn of httpd with no changes)


 I'm surprised it is an ap call and not an apr call, but
I am not a web server programmer!


I agree, it took me a while to find the call again because I keep searching for apr_.

Brian

Thread (31 messages)

« previous php.internals (#17874) next »