At 11:00 AM 8/21/2003 -0500, you wrote: >OK, ok, I know, a real operating system should not crash if an app >misbehaves. I did say it was Off Topic. > >Apparently Service Pack 3 for M$ 2000 Server causes the Performance Monitor >to return incorrect results. Service Pack 4 is available, but there is no >info available on if this fixes the Performance Monitor error.
I hadn't heard of this. Can you provide the Knowledge Base article for this? Assuming you WERE able to use perfmon then look at Committed Bytes. It will increase over time if you have a leaky application. If not, try using pslist from sysinternals.com, which has a mem column. Just run pslist in a script every n minutes, making sure to match process name and PID. You can then graph out the value of mem over time and see what the heck is going on. There are some tools in the Win2k RK for this, but I think pslist is going to be easier on you. For those not in the know, if you are managing Windows machines then many of the tools at sysinternals.com are a must. If nothing else they are very helpful when writing scripts. For example, I call pslist via perfmon whenever CPU usage gets too high. This is an easy way to get a snapshot of the system. For learning more about Windows performance tuning I would suggest O'Reilly & Associates' _Windows 2000 Performance Guide_ by Friedman and Pentakalos. --- Dustin Puryear <[EMAIL PROTECTED]> Puryear Information Technology, LLC <http://www.puryear-it.com> Providing expertise in the management, integration, and security of Windows and UNIX systems, networks, and applications.
