Message-ID: <47971A66.4C0A137@dessent.net>
Date: Wed, 23 Jan 2008 02:43:50 -0800
From: Brian Dessent <brian@dessent.net>
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: ps executable does not appear to match source
References: <4a89b8680801222033y6dad8c6dw31f71e10896117c5@mail.gmail.com> <2ce9650b0801230134n26c41524y7649837692dff7ff@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: cygwin@cygwin.com
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Chris January wrote:

> I would rather see a patch that added Windows pids to /proc than only
> to procps. Then the functionality would be available to other
> programs, like top.

Agree.

> To support scripts that rely on the format and options of the old
> Cygwin ps we could add a new 'Cygwin' personality to procps.

Ugh.  It seems to me like 'ps' has already been littered with so many
incompatible or conflicting option sets over the years that perpetuating
yet another into history seems like a travesty.  Can't we just add
support for -W to procps for WINPID and then declare that Cygwin's 'ps'
option set is now the same as Linux's?  After all, WJM.  As far as
options, the common ones (-a/-e/-l/-f/-p/-u) seem to overlap mostly; the
column order and layout are of course slightly different between the two
but I can't really see a portable script being able to rely on that
anyway.

Brian

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