On Thursday 02 August 2007 16:18, Dossy Shiobara wrote: > On 2007.08.01, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > One of the hallmarks of AOLserver has always been ease of configuration. > > My sense is that we're drifting away from that? > > Frankly, one of the biggest FAQ's is "how do I tune AOLserver?" IMHO, > "ease of configuration" is "less to manually tune" which means settings > need to be able to be adjusted at runtime. > > Seriously, what value does being able to set max connections manually > really offer? What people really want is a server that uses resources > efficiently but in a way which doesn't run itself out of resources and > starve itself. Rarely do I actually hear people say "yes, I really want > to limit the number of connections" but rather "I want to allow as many > connections as my hardware can handle--how high should I set > max connections?" > > AOLserver is going to become even easier to set up and configure. These > are growing pains, unfortunately.
What needs to grow here is your concept of community and just common sense. Somehow you conceive that the ability to change parameters without a restart, or to set them via a configuration setting are incompatable with each other. Then you invoke some fantasy magic code. But here is quite a riddle: you claim that everyone wants to max out their server, but then one of the new 'features' in 4.5 is ns_limits. What The Fuck! Also, I should note that the purpose of ns_pools is to distribute resources, so your whole reason is full of shit. The truth is that one large drawback of server management is 'managing' resources. So please spare us your philosophy of magic-ware that is smarter than the developers on this list. If the writers of this code can make such fundamental mistakes as we see here, we need real help. With logic like this who could ever expect code to work? The upside is that we now have a better idea of who we are dealing with. Thanks for cluing us in that we have no reason to believe things are going to be okay. Something has to change here. Either AOL needs to come clean, level with the community, or we need to simply inform hapless developers what they should expect. The community really should enforce public discussion of anything included in AOLserver, and more important enforce standards of compatability, upgrade pathways, etc. _OR_ we should notify everyone who comes near that it isn't really public development. This really sucks. tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
