On 2003.08.09, Jim Wilcoxson <[EMAIL PROTECTED]> wrote: > [ns_info pid] does return the parent nsd process on 3.4.
There is only one nsd process. If you're talking about Linux, those seperate "processes" aren't really going to tell you much, as I recall. > On a production system, when top or ps shows an nsd process chewing up > 90% of a CPU, it would be useful to relate that to server.log entries. > Or something. Right now it can't be related to anything. The parent > nsd's process number isn't useful in this situation. What do you have going to your server.log? Why is it bad when nsd uses 90% of the CPU? Don't you want to be getting your money's worth? (Yes, I want to pay for 100% of something and only use 50% of it! I just recently bought the Brooklyn Bridge, too ...) If you have bottlenecks in your web applications, then instrumenting your app. code to reveal where the bottleneck is ... that's a more interesting, and feasible, problem to solve. -- Dossy -- 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.
