X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=WXPgNREu83Y7nl8Oa1LQx54XLj1K
	7tjofHKtrt+nlYsx5V+kLWfumKdVGM5Vj7Dg4fhei+gYCYC0OwnfKi9MPGggCTLJ
	229nJC4ybYzsFZGupibuq2xeDFRDsz4gWv6ZHMyxINyvjA+ayVHU80Nwwnuhgsky
	6wjrYNZD5GrHAtw=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; s=default; bh=mbuIJW19ashQ5G6u2uAWFNb+p4s=; b=Ll
	Nsz2HU6VljAQ1M1dSu8GnqN3fkkIJ5fqrKB6GJ9tu/C7Jo1T6BSqzrmiIBcWoW26
	Dwfuw2fAhNxezOw3GhAW2GUoypD2POZysT032IB4iLWuO87fLB0hYmkHm8vCsJZw
	7WknWwWcGfmKS0XDVM2t2zZghJJFVDMKSC96UKOXU=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO: etr-usa.com
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: ps questions
From: Warren Young <wyml AT etr-usa DOT com>
In-Reply-To: <20141218171116.GF10824@calimero.vinschen.de>
Date: Thu, 18 Dec 2014 10:26:20 -0700
Message-Id: <8F8B22BA-B007-4F10-9B4F-9BD963D17059@etr-usa.com>
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>
To: cygwin AT cygwin DOT com
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id sBIHQa9G014334

On Dec 18, 2014, at 10:11 AM, Corinna Vinschen <corinna-cygwin AT cygwin DOT 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