Michael, There seems to be more serious issues which need to be addressed (hopefully I am wrong):
1. how can you verify how a pool is mapped, and if it is really being used? 2. if you have multiple virtual servers, it appears that the last one loaded overwrites the values of previous servers. For instance, the error.log file has this: from server 'jnm', loaded first [-main-] Notice: default Pool: minthreads 0 maxthreads 0 idle 0 current 0 maxconns 0 queued 0 timeout 120 [-main-] Notice: ns_pools registered default jnm GET / [-main-] Notice: ns_pools registered default jnm POST / [-main-] Notice: fast Pool: minthreads 2 maxthreads 10 idle 0 current 0 maxconns 100 queued 0 timeout 120 [-main-] Notice: ns_pools registered fast jnm GET /*-thumb.jpg [-main-] Notice: ns_pools registered fast jnm GET /images/*-thumb.jpg [-main-] Notice: ns_pools registered fast jnm GET /test.html .... from server 'tutos', loaded last [-main-] Notice: default Pool: minthreads 4 maxthreads 11 idle 0 current 0 maxconns 99 queued 0 timeout 123 [-main-] Notice: ns_pools registered default tutos GET / [-main-] Notice: ns_pools registered default tutos POST / [-main-] Notice: fast Pool: minthreads 3 maxthreads 11 idle 0 current 0 maxconns 101 queued 0 timeout 125 [-main-] Notice: ns_pools registered fast tutos GET /*-thumb.jpg [-main-] Notice: ns_pools registered fast tutos GET /*-thumb.gif nscp output: Welcome to jnm running at /web/nsd45/bin/nsd (pid 27920) AOLserver/4.5.0 (aolserver4_5) for linux built on Jan 2 2007 at 08:12:17 CVS Tag: $Name: $ jnm:nscp 1> ns_pools list default fast error jnm:nscp 2> ns_pools get default minthreads 4 maxthreads 11 idle 4 current 4 maxconns 99 queued 0 timeout 123 jnm:nscp 3> ns_pools get fast minthreads 3 maxthreads 11 idle 3 current 3 maxconns 101 queued 0 timeout 125 jnm:nscp 4> exit Welcome to tutos running at /web/nsd45/bin/nsd (pid 27920) AOLserver/4.5.0 (aolserver4_5) for linux built on Jan 2 2007 at 08:12:17 CVS Tag: $Name: $ tutos:nscp 1> ns_pools get default minthreads 4 maxthreads 11 idle 4 current 4 maxconns 99 queued 0 timeout 123 tutos:nscp 2> ns_pools get fast minthreads 3 maxthreads 11 idle 3 current 3 maxconns 101 queued 0 timeout 125 tutos:nscp 3> exit So both server now have the same configuration for similarly named pools, even though the ns_pools get command displayed the correct information during startup. tom jackson On Wednesday 01 August 2007 15:24, Michael Andrews wrote: > Tom - I'll take a look at the code in more detail this week. Here are > my initial thoughts: > > One of the benefits of having a Tcl command to manage pools is that > you do not need to use the server config. A Tcl module or package > can 1) create a pool, 2) register the pool, and 3) throttle the > params as needed at run-time. The only reason to do the pools.tcl > was to set the default pool's params with that from the config in an > attempt to make it backward compatible. > > So personally, I think a "foo" pool would be better off created and > managed by a "foo" Tcl package or module. The config then stays clean > - and all "foo" logic and needs are encapsulated, easer to rev/update/ > release etc. > > Thoughts? > > M > > On Aug 1, 2007, at 5:39 PM, Tom Jackson wrote: > > I've just confirmed maxconnections from an old config file, > > although I guess > > the real answer would be in the C code. > > > > Are you going to commit my additions to the file? > > > > tom jackson > > > > On Wednesday 01 August 2007 14:21, Michael Andrews wrote: > >> I'll install 4.0.10 this week, confirm the param, and change if > >> needed. It is probably time to do a better base.tcl (server.cfg) > >> file. I will do that this week too. > > > > -- > > 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. > > -- > 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. -- 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.
