MIME-Version: 1.0
In-Reply-To: <050f01ca9b07$df859370$9e90ba50$@com>
References: <050f01ca9b07$df859370$9e90ba50$@com>
Date: Fri, 22 Jan 2010 05:02:03 +0000
Message-ID: <416096c61001212102q8b38104s814fd15688957d3a@mail.gmail.com>
Subject: Re: Why require ps -W and kill -f
From: Andy Koppe <andy.koppe@gmail.com>
To: don@beusee.com, cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
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

2010/1/22 Don Beusee:
> ps -e on Unix displays =E2=80=9Cevery process running on the system=E2=80=
=9D.=C2=A0 This command
> doesn't do that under cygwin.=C2=A0 Why should it be necessary to supply =
-W to
> see all processes running on the system?

Because those processes are not Cygwin/Unix processes. In particular,
they do not have Cygwin process IDs. Cygwin PIDs and Windows PIDs are
different concepts (even though they often coincide), and that's
because multiple windows processes can be needed to emulate one Cygwin
process. For example, when calling exec(), the new program is
conceptually executed in the same Cygwin process, but actually a new
Windows process has to be created since Windows doesn't allow a
process to change executable.

Andy

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