Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Mime-Version: 1.0
X-Sender: rschulz AT pop DOT teknowledge DOT com
Message-Id: <p04330100b6144aa4d961@[192.168.0.29]>
In-Reply-To: <4.3.2.7.0.20001018231152.00c70100@pop.bresnanlink.net>
References: <4 DOT 3 DOT 2 DOT 7 DOT 0 DOT 20001018223411 DOT 00c75c50 AT pop DOT bresnanlink DOT net>
 <4 DOT 3 DOT 2 DOT 7 DOT 0 DOT 20001018221146 DOT 00c6f190 AT pop DOT bresnanlink DOT net>
 <5206-Wed18Oct2000223844+0100-starksb AT ebi DOT ac DOT uk>
 <2443-Wed11Oct2000213946+0100-starksb AT ebi DOT ac DOT uk>
 <20001011164208 DOT A13281 AT cygnus DOT com>
 <5206-Wed18Oct2000223844+0100-starksb AT ebi DOT ac DOT uk>
 <20001018225426 DOT B15652 AT cygnus DOT com>
 <4 DOT 3 DOT 2 DOT 7 DOT 0 DOT 20001018221146 DOT 00c6f190 AT pop DOT bresnanlink DOT net>
 <20001018232320 DOT D15926 AT cygnus DOT com>
 <4 DOT 3 DOT 2 DOT 7 DOT 0 DOT 20001018223411 DOT 00c75c50 AT pop DOT bresnanlink DOT net>
 <4 DOT 3 DOT 2 DOT 7 DOT 0 DOT 20001018231152 DOT 00c70100 AT pop DOT bresnanlink DOT net>
Date: Thu, 19 Oct 2000 00:03:26 -0700
To: Chris Abbey <cabbey AT chartermi DOT net>, cygwin AT sources DOT redhat DOT com
From: Randall R Schulz <rschulz AT teknowledge DOT com>
Subject: Re: ps output format
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-MDaemon-Deliver-To: cygwin AT sources DOT redhat DOT com
X-Return-Path: rschulz AT teknowledge DOT com

TWIMC,

I have no idea what would be the implications of or requirements for 
implementing it under Cygwin, but the /proc file system is the way to 
free programs of parsing "ps" and related program output. Even though 
/proc doesn't solve the problem of standardizing the information 
content itself (since the contents of the files in /proc are 
system-specific and tend to change with new releases of the system 
that creates that data), but it does free programs from having to 
decode output that is intended primarily for human consumption as 
well as free them from having to run sub-processes to acquire that 
information.

Randall Schulz
Teknowledge Corp.
Palo Alto, CA USA


At 23:17 -0500 10/18/00, Chris Abbey wrote:
>At 23:51 10/18/00 -0400, Christopher Faylor wrote:
>>If you are aware of an existing ps implementation that does this,
>>though, I wouldn't mind a patch to have ps emulate it.  The ps code is
>>really pretty simple so it should not be hard to modify.
>
>there are none. any new format I came up with would be unique, and
>I'd have to hope the others would adopt it... some would (justifably)
>tell me to use their format specifier... but that just leads back to
>the same path because the format specifier isn't spec'd and so they
>all use subtly different options. I spent almost a month trying to
>port a really great script called top10vms so that it would run under:
>cygwin, aix, solaris, hp/ux, reliant, and linux. I eventually gave up
>even trying to get it to *work* on reliant and hp/ux, and the others
>were eventually done with the equivalent of #ifdefs. The net that I
>learned is that some platforms have RUN OUT of option letters for ps.
>The day I learned ps -a, ps -A, ps a, and ps A are all legal and
>completely different on the same box with the same binary is the
>day I lost it.



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com