X-Recipient: archive-cygwin@delorie.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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=uv0YGbCtmqzs6su1UZNbAZFMAlEUebN8o+MZ3T6mn9jd6yBzzBMtt
	iSWeH8TpGx7smzC9HTV5odoJdvweucPvz6SMuzK9E44/qqlhqeH14S6yldvph932
	1KLPYd4fZT8iRESgT6g955mzYnplb4WZa1B+WzC+Eoww0X81ek0LQ4=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=Hj0ZhjPAh4bpEIh7OYvLS5OikvM=; b=dVTCECT2wWVXgKe0VsfnfVud3Blt
	pXfLdeLgzkjRAB71Bw7ngCY91Mu6k4RzCTxtx2IPjKMuvPPoSu/4o+RhH1LW8oDJ
	4c03hrr3z1eM2zwixreWVIRN8vYPNR0qqH+tfIy/ifwZjFAmwYs23HbUeHe2akxc
	T59oPm4YhhdtkHM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-101.9 required=5.0 tests=AWL,BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=died, H*c:application
X-HELO: drew.franken.de
Date: Wed, 7 Jun 2017 20:58:12 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: PPID in ps -efW not accurate
Message-ID: <20170607185812.GE13513@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <CACoZoo2YQDaQOxDZPLZKwVRJNDNkywXUh5YoP97jOx9rRf3YaQ@mail.gmail.com> <20170607173153.GC13513@calimero.vinschen.de> <CACoZoo2oMQOdo-NxC8hGvDaXLQ=fF18c1ho+pmxKmYeqAE7myg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="x4pBfXISqBoDm8sr"
Content-Disposition: inline
In-Reply-To: <CACoZoo2oMQOdo-NxC8hGvDaXLQ=fF18c1ho+pmxKmYeqAE7myg@mail.gmail.com>
User-Agent: Mutt/1.8.0 (2017-02-23)

--x4pBfXISqBoDm8sr
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Jun  7 13:47, Erik Soderquist wrote:
> On Wed, Jun 7, 2017 at 1:31 PM, Corinna Vinschen  wrote:
> > Worse, given the fact that Windows reuses PIDs quickly after a process
> > died, this information can be totally wrong.
>=20
> I was not aware Windows would reuse a PID when children of the
> previous process still existed...

Cygwin was bitten by this problem way back when.  We workaround this by
making sure to keep an open handle to the parent, even if the process
exited.  Other Windows processes don't, so you're bound to run into
problems when relying on that info.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--x4pBfXISqBoDm8sr
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJZOEzDAAoJEPU2Bp2uRE+gt/8QAJm3OJhKS3mBfbmq3/htH33O
vLCOEcEkhkKu64/BG/qFY3EH4KfQQnYGt+zpJejxgyMZb88+0TJfiuhXdkKZmAZK
KiMyQenK2VRp7TRiORn3G2bP38Ay/F/ae+u3nNNenkKzn88X63Fz3FuNn1s9V/SS
wWcd9TBDOzKzWPMgqbKETPNALoPWFnNB1ri32aB8tqdhVP5CZo983Yw9+/2J79K5
GDvBvL1+VGwAUbQeg92nv4eDUHtWI9X2l17AuCyFedQEgKTJj9ZylQE+3zZXguYi
QUO62th00JUG/BgscRY7iFbYhuRRkhdlXNNNwfyiu5kclTnszqV/V2QgVVHAZwkV
v8VvwGz2a6DK7KCa+rfxVjNrObh63GLiqsEg6JLXX/viDkTbdAAXmu8DTxFfyamd
2rauKBWxET6XCGMupYFSMl3aPUKdu8cZN4GteiNMWV6PFbs8WYnVyN7phjVBKeLO
9e2oXx38aeS3CjeiA9yHUKqM0ZkGlIAKwxv6SUrnwO15/ivFxrOeDs6Z9kHgSAPL
gyratPuCbCeM3wc22yvp28MnQknkdkwQ76FIEKiN0z/WWPCNrucVDPcfn5+lDWRP
0AnlVhsHkopNJpbcPx151Pl1goztVc3qCAPJk3uR5UUk4niM99BlTSWQ1DZ2cxmJ
F4gxbuBSAcmvaYDnCbvS
=bkD1
-----END PGP SIGNATURE-----

--x4pBfXISqBoDm8sr--
