Hi,
The code for "ns_info threads" looks about the same in 4.0 and 4.5 and
it doesn't look super safe. It does have a lock around walking the
list of threads but there are place where it copies data from strings
which may be changing. And, like "ns_server active", it's really
designed for live diag work, not so much as a background health check.
-Jim
On May 31, 2009, at 7:53 PM, Sep Ng wrote:
I'm handling aolserver 4.0.10 and yeah, I know it's kind of old. If
I'm not mistaken, ns_info threads was not totally thread safe in that
version and it caused quite a few crashes here. I think I've managed
to get that number of crashing down a bit with mutex and a bit of
aolserver 4.5 code, but it still does happen. I'm wondering though if
ns_info threads was meant to be written as a proc for diagnosing
AOLserver or if it's safe to use to periodically check AOLserver for
running threads.
--
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.
