This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: ps questions
- From: Warren Young <wyml at etr-usa dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 18 Dec 2014 10:26:20 -0700
- Subject: Re: ps questions
- Authentication-results: sourceware.org; auth=none
- References: <CAO2ddnZChb-n9+Z1YEWCFSA=WTaYfkmHdjMZk7Te5JYckUDE+Q at mail dot gmail dot com> <5492EDFC dot 5080608 at gmail dot com> <CAO2ddnZHs=4GxUJtjgoyTXO2Or3oKzY6Rck=m9Mqfj6DgWUQUg at mail dot gmail dot com> <20141218171116 dot GF10824 at calimero dot vinschen dot de>
On Dec 18, 2014, at 10:11 AM, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
> The <defunct> information is fetched from the process itself. This
> requires a living, valid Cygwin process, so the info isn't available for
> Windows processes.
On a Unix/Linux system, a process is marked <defunct> when the kernel knows it has died, but its parent hasn’t called wait(2) or similar yet, so the kernel keeps info about the process around with the expectation that this call will come later.
So, you’re saying that Cygwin doesn’t do something similar?
If it did, it would be able to distinguish between dead Cygwin processes and dead native processes. “I didn’t start that one, so I will mark it <dead> instead of <defunct>,” kind of thing.
--
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