Erik Bray wrote:
On Tue, Feb 14, 2017 at 8:25 PM, Mark Geisert <x...@xxxxxx.xxx> wrote:
Please don't quote raw email addresses. We try to avoid feeding spammers.
Erik Bray wrote:
The attached Python script
??
D'oh! Here is the script. It at least demonstrates the problem.
[...]
Thanks! Running this script repeatedly on my system (Win7, 2 cores / 4 HT
threads) showed no differences between your Test 1 and Test 2. Each Test
concludes in one of three ways, seemingly randomly: (1) read of /proc/<pid>/stat
succeeds and process status is displayed, (2) read fails with Python IOError,
(3) read apparently succeeds but there's no process data displayed.
An strace of your script shows Python itself is calling wait4() to reap the
child process. So, as Doug suggested on another thread, the script's actions
are just subject to the whims of process scheduling and vary from run to run.
..mark
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
