Of course, I responded but didn't actually answer your question. Yes,
the patch should also fix the cases where you see 100% CPU utilization
even with maxkeepalive set to 0. For, well, the obvious reason ...
-- Dossy
On 2004.08.24, Dossy Shiobara <[EMAIL PROTECTED]> wrote:
> On 2004.08.24, Torben Brosten <[EMAIL PROTECTED]> wrote:
> > Dossy, is this patch supposed to work for 100% CPU util. cases where
> > maxkeepalive is 0 in the config.tcl?
> >
> > ns_section ns/parameters
> >
> > ns_param maxkeepalive 0
>
> Sadly, it seems that in at least the 4.0 codebase, that configuration
> setting doesn't do anything. See:
>
> $ fgrep maxkeep */*.[ch]
> nsd/nsconf.c: nsconf.keepalive.maxkeep = GetInt("maxkeepalive",
> KEEPALIVE_MAXKEEP_INT);
> nsd/nsd.h: int maxkeep;
>
> Nowhere else in the code do we use nsconf.keepalive.maxkeep. Heh.
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
--
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.
