Message-Id:	<200508042155.j74LtbRA026728@delorie.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
From:	"Herb Martin" <HerbM AT learnquick DOT com>
To:	"'Cygwin List'" <cygwin AT cygwin DOT com>
Subject:	RE: pid confusion and pstree (Attn: User's Guide maintainer)
Date:	Thu, 4 Aug 2005 16:55:29 -0500
MIME-Version:	1.0
In-Reply-To:	<Pine.LNX.4.62.0508041704070.27688@ns.pyerotechnics.com>

Jason Pyeron wrote>
> I did read the man page for ps, first, before posting.
> 
> I does not say that the cygwin pid will be changed to the 
> windows pid for cygwin processes. It does indicate for 
> windows processes the PID is the same as the WINPID and can 
> be used in kill -f.


I am a Cygwin beginner too, so if this is not useful
to your discussion just ignore this message:

In my limited experience the PID and the WINPID are 
always (?) the same for Cygwin processess INITIALLY.

After a HUP signal (kill -s HUP pid, my Cygwin process
(if it survives) will have the SAME PID but a new WinPID.

I use this fact to assure myself that I have succeeded
in the HUP to get Exim and other programs to reload their
configuration.

--
Herb


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -