Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 6 Aug 2002 11:26:23 +0100 From: Jim George To: cygwin AT cygwin DOT com Subject: Re: Top reporting on cygwin processes only? Message-Id: <20020806112623.2950e6f5.jim.george@blueyonder.co.uk> In-Reply-To: <20020806095533.O3921@cygbert.vinschen.de> References: <20020805223042 DOT 39e9de67 DOT jim DOT george AT blueyonder DOT co DOT uk> <20020806095533 DOT O3921 AT cygbert DOT vinschen DOT de> Organization: JSDM Services Ltd Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Tue, 6 Aug 2002 09:55:33 +0200 Corinna Vinschen wrote: > On Mon, Aug 05, 2002 at 07:10:50PM -0400, Igor Pechtchanski wrote: > > P.S. Top walks the process table in the same way ps does. It shouldn't > > No. ps uses the Cygwin API, top uses /proc. /proc only contains Cygwin > processes. > > Corinna > Questions then... should ps be modified to work as top does, of course /proc would need to be upgraded, or can top be modified to work as ps does, or should both continue on their own but be updated to recognise all processes running on a box? Jim -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/