Right Gaustaf, I don't find it either, it seems it was just there till 3.x
one of the thread which I found generated by you.
http://www.mail-archive.com/aolserver@listserv.aol.com/msg07000.html
I will just remove that param and will keep only keepwait in params.
Regards,
Majid.
On Sat, Apr 16,
I still don't get, what your are doing with "MaxKeepAlive",
but i don't have to. Be aware, that aolserver does not use
it as a config variable (just do a "fgrep -Ri MaxKeepAlive
." in the src directory). If your application uses
MaxKeepAlive (from tcl, or from one of your c-modules), it
is fin
Hi Gaustaf,
Thanks for clarifying the maxrun param. About Tcl variables this is how I am
using them:
ns_section "ns/encodings"
ns_param .adp "utf-8"
ns_param .byt "utf-8"
set myserver_root "/myserver"
set max_threads 40
set max_conns 1000 ;# or ConnsPerThread, i.e. after how many
Hi Majid,
maxrun is one way to limit the maximum number of concurrent
connections. It allows to limit certain kinds of requests
(actually the queueing of incoming requests). See the
naviserver man page for an example
http://naviserver.sourceforge.net/n/naviserver/files/ns_limits.html
If
