MIME-Version: 1.0
In-Reply-To: <5a05e0e60911270759o6ee6f09o7bfd9bf3f46a0d4f@mail.gmail.com>
References: <5a05e0e60911261052w2e60586cxe7a90d02b4cf6e0f@mail.gmail.com> 	 <5a05e0e60911262123g762a172sa02913109e2f27bd@mail.gmail.com> 	 <4B0F832D.5030405@columbus.rr.com> 	 <5a05e0e60911270758o7d543587h7402ea98fef62be3@mail.gmail.com> 	 <5a05e0e60911270759o6ee6f09o7bfd9bf3f46a0d4f@mail.gmail.com>
Date: Fri, 27 Nov 2009 11:51:00 -0500
Message-ID: <5a05e0e60911270851m5844ff5fl87643322977d200@mail.gmail.com>
Subject: Re: Defunct processes with 1.5.25-15; seemingly reproducible
From: Dave Steenburgh <dave.steenburgh@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Dave Steenburgh wrote:
> 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.

I started a new session just minutes ago.  The process that parses my
data and pipes commands to gnuplot happened to have a PID of 5240.  ps
indicated that PID 5240 was defunct, and all the other information
appears the same (though the timestamp is now a date).  Although the
process was not actually defunct, I killed that session and started a
new one.  The process with the same name of course has a new PID, but
it is /not/ listed as defunct.  Whatever is the cause of the first
defunct processes, it seems [to me] that the more recent ones have a
different cause.

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