Here's the specific issue I'm trying to address with SingleListen, and
the entire mutex-at-runtime... I build one version of Apache and
implement it on my suite of servers, say all are running OS Foo 3.4.
Now some of those servers are single CPU, some are multiCPU. I'd like
to avoid having separate builds for individual machines. Now say that
3.5 comes out, and it supports S_L_U_A... I install it on some
machines, but not all. It would be nice to be able to continue to use
the same build of Apache for those as well. I want to give sys-admins
finer control and avoid the need for recompiles as much as possible.
True, the probability (and usefullness) of the latter is a bit less
than the former, but it would be nice, and it's a logical extension
of the concept.
I'm not going to "fight" for it if it sacrifices the AcceptMutex
stuff. *THAT* is a real, obvious need, and anyone who doesn't think
so has never actually *used* Apache in a sys-admin/webmaster
environment.
--
===========================================================================
Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/
"A society that will trade a little liberty for a little order
will lose both and deserve neither"
