X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Message-ID:	<4a89b8680801180616s3adb9071ndc8ab96e354a381c@mail.gmail.com>
Date:	Fri, 18 Jan 2008 08:16:57 -0600
From:	paul DOT hermeneutic AT gmail DOT com
To:	cygwin AT cygwin DOT com
Subject:	Re: ps executable does not appear to match source
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

> On Jan 17, 2008 9:38 PM,  <> wrote:
> > The ps that comes with Cygwin is missing a number of features that
> > appear to be in the procps-3.2.7/ps/ source code.  The source code
> > does not look like it was used to build the executable.  Is this
> > correct?
>
> Cygwin has both ps and procps available.  The ps in Cygwin has the
> advantage of showing Windows processes, too.  The procps is just what
> you'd expect.
>
> -Jason

The ps from procps appears to be what is in use on Linux.  Why is the
ps for Cygwin not built from this?

From which package is the ps in Cygwin built?

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