Author steve.dower
Recipients ammar2, giampaolo.rodola, jkloth, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2018-07-18.15:00:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1531926035.03.0.56676864532.issue34060@psf.upfronthosting.co.za>
In-reply-to
Content
> wmic cpu ...

This is the WMI solution we are trying to avoid.

But then again, if it's solely for our tests, perhaps the best way to approach this is to start a Python thread that periodically runs this command?

I also haven't seen it suggested, but perhaps GetProcessTimes (https://docs.microsoft.com/en-us/windows/desktop/api/processthreadsapi/nf-processthreadsapi-getprocesstimes) (or GetThreadTimes) would provide enough information to detect the same information?
History
Date User Action Args
2018-07-18 15:00:35steve.dowersetrecipients: + steve.dower, paul.moore, vstinner, giampaolo.rodola, tim.golden, jkloth, zach.ware, ammar2
2018-07-18 15:00:35steve.dowersetmessageid: <1531926035.03.0.56676864532.issue34060@psf.upfronthosting.co.za>
2018-07-18 15:00:35steve.dowerlinkissue34060 messages
2018-07-18 15:00:34steve.dowercreate