On Fri, Dec 11, 2009 at 09:40:53AM -0800, Bernard Li wrote:
> 
> Wow...  what a long thread...

Sorry about that boss, but also sent an "executive" summary in :

  
http://www.mail-archive.com/[email protected]/msg05398.html

Hope you don't mind reading instead that one or my small enough for a tweet
comment on the STATUS page for 3.1

> IMHO, the best solution here is to look at apache's main loop
> implementation and adapt our code.  This way, (hopefully) we will get
> what we want (late initialization) without modifying any apr code.
> Carlo, since you seem to be on a roll here, could you please kindly:

I think I'd made my point of view clear, including alternatives and a probe
of concept implementation of my preferred resolution which still keeps a
"fix" for the problem this regression was meant to help with.

If you are interested on implementing alternative 3 (if that is even possible)
or 4 feel free to do so, but considering this is a showstopper for 3.1.6 and
that we (would assume) want to get that released without regressions and ASAP
then would recommend instead we focus for now in a fix for this regression
which will mean either :

1) revert the code and delay a solution for the child notification issues
2) implement the child notification using something we know works like the
   code proposed (at least for now) instead of reordering the initialization
   and breaking all the BSD (and who knows what else) with that.

Carlo

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Ganglia-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ganglia-developers

Reply via email to