public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Problem with zombie processes
Date: Fri, 17 Feb 2017 22:06:00 -0000	[thread overview]
Message-ID: <58A773C9.1080905@maxrnd.com> (raw)
In-Reply-To: <CAOTD34Z7VM=6=Ss_gCLS97c4sFNpnaT-+RgJq+xme-VyWYbbpw@mail.gmail.com>

Erik Bray wrote:
> On Tue, Feb 14, 2017 at 8:25 PM, Mark Geisert <XXXX@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

  parent reply	other threads:[~2017-02-17 22:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 11:14 Erik Bray
2017-02-14 19:25 ` Mark Geisert
2017-02-17 11:00   ` Erik Bray
2017-02-17 15:06     ` Doug Henderson
2017-02-17 22:06     ` Mark Geisert [this message]
2017-02-20  9:46       ` Erik Bray
2017-02-20 10:54         ` Mark Geisert
2017-02-20 15:23           ` Erik Bray
2017-02-20 22:54             ` Mark Geisert
2017-02-21 11:59               ` Erik Bray
2019-04-04 12:44                 ` E. Madison Bray

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=58A773C9.1080905@maxrnd.com \
    --to=mark@maxrnd.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).