Bug in win32all-128 with multiprocessor NT
Mark Hammond
mhammond at skippinet.com.au
Sat Feb 26 16:32:58 EST 2000
More information about the Python-list mailing list
Sat Feb 26 16:32:58 EST 2000
- Previous message (by thread): Bug in win32all-128 with multiprocessor NT
- Next message (by thread): Style, readability and docstrings
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I have - it is wierd. If you start the NT perfmon, you will sometimes see strange names - eg, an added trailing "_". If you pass the same name you see in NT Perfmon (which may not be the name you expect to use!) then Python works fine. This leads me to point to simply a perfmon strangeness rather than a problem in the extensions... Mark. "Rodgers, Kevin" <KRodgers at ryanaero.com> wrote in message news:0D8C1A50C283D311ABB800508B612E5354B39C at ryanaero.com... > How strange! Maybe this is a difference between NT 4.0 and Win2K. I've > never had a problem with the FindPerformanceAttributesByName function . . . > > > -----Original Message----- > > From: Darrell [SMTP:darrell at dorb.com] > > Sent: Thursday, February 24, 2000 8:44 PM > > To: Rodgers, Kevin > > Cc: python-list at python.org > > Subject: Re: Bug in win32all-128 with multiprocessor NT > > > > > > > > > The "pname" is to be replaced by whatever process name you want to try > > this > > > on. For example, if you have the NT version of XEmacs running, the line > > > would look like: > > > pid = win32pdhutil.FindPerformanceAttributesByName("xemacs") > > > > > Yelp that's what I did. Tried with and without the ".exe". It just sits > > there for about 15sec > > ,chewing up CPU then returns []. > > > > --Darrell > > >
- Previous message (by thread): Bug in win32all-128 with multiprocessor NT
- Next message (by thread): Style, readability and docstrings
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list