X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 	tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <5a05e0e60911270758o7d543587h7402ea98fef62be3@mail.gmail.com>
References: <5a05e0e60911261052w2e60586cxe7a90d02b4cf6e0f AT mail DOT gmail DOT com> 	 <5a05e0e60911262123g762a172sa02913109e2f27bd AT mail DOT gmail DOT com> 	 <4B0F832D DOT 5030405 AT columbus DOT rr DOT com> 	 <5a05e0e60911270758o7d543587h7402ea98fef62be3 AT mail DOT gmail DOT com>
Date: Fri, 27 Nov 2009 10:59:53 -0500
Message-ID: <5a05e0e60911270759o6ee6f09o7bfd9bf3f46a0d4f@mail.gmail.com>
Subject: Re: Defunct processes with 1.5.25-15; seemingly reproducible
From: Dave Steenburgh <dave DOT steenburgh AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

Paul McFerrin wrote:
> A <defunct> process is not necesarily the real "problem". =A0All <defunct>
> process are processes that their parent has NOT done a wait(2) yet. =A0Si=
nce
> these <defunct> processes have called exit(2), they must hang around unti=
l a
> wait(2) is completed so that the exit status can be returned to the paren=
t.
>
> =A0 You need to understand more of the parent/child relationship before
> =A0 you can pass blame, if any.

Personally, I'm not trying to blame anyone. =A0I'm trying to figure out
what the real problem is, but I'm not familiar enough with the details
to track down the real problem. =A0How about this...is there any way
that I can be absolutely certain which process was the parent?

And what is the significance of the duplicated lines that ps showed
me? =A0Each of three processes did indeed have a lock on an output file
from the most recent session, and yet all the information that ps
showed was identical to a previous session.

--
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