Closed GoogleCodeExporter closed 8 years ago
Setting 0.2.1 milestone for now.
First we have to figure out what kind of information we want to provide exactly.
Other than just the number of threads one might want to have a "thread object"
and do something with it, like getting its id or killing/suspending the thread
in which case the implementation gets a lot more complicated than just reading
/proc.
Original comment by g.rodola
on 2 Nov 2010 at 1:33
My vote would be just to have number of threads as a metric, at least for now.
I can't really see killing/suspending or otherwise tampering with threads for a
running process from psutil, but if for some reason we do decide to do that we
can implement that later.
Original comment by jlo...@gmail.com
on 2 Nov 2010 at 6:49
It turned out we need exactly this at work to debug a nasty bug in our web app
build on top of paster web server. =)
For this reason I'm re-setting milestone to 0.2.0.
Original comment by g.rodola
on 8 Nov 2010 at 5:35
Original comment by g.rodola
on 8 Nov 2010 at 5:35
Implemented for Linux in r776.
Original comment by g.rodola
on 8 Nov 2010 at 5:59
FreeBSD implementation committed in r777.
Original comment by g.rodola
on 8 Nov 2010 at 6:29
Implemented on Windows in r778.
Original comment by g.rodola
on 8 Nov 2010 at 7:59
Implemented OS X in r780. Marking as FixedinSVN
Original comment by jlo...@gmail.com
on 10 Nov 2010 at 6:43
Original comment by g.rodola
on 13 Nov 2010 at 3:14
[deleted comment]
Updated csets after the SVN -> Mercurial migration:
r776 == revision ef885d0b59e7
r777 == revision 76bbbdc1fb05
r778 == revision e895105faa04
r780 == revision 8cf0eab3db3c
Original comment by g.rodola
on 2 Mar 2013 at 11:56
Original issue reported on code.google.com by
fritz....@gmail.com
on 2 Nov 2010 at 1:06