Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Sat, 27 Jul 2002 08:51:53 +0100
From: Jim George <jim DOT george AT blueyonder DOT co DOT uk>
To: cygwin AT cygwin DOT com
Subject: Re: a way to read the current cpu load from the shell or via a  cmdline utility in cygwin?
Message-Id: <20020727085153.0b5bbf8b.jim.george@blueyonder.co.uk>
In-Reply-To: <005201c234e5$cd9f4ec0$0100a8c0@atomice.net>
References: <NCEBJJFMCAOKNNABBFIMOEPMCDAA DOT john DOT r DOT morrison AT ntlworld DOT com>
	<005201c234e5$cd9f4ec0$0100a8c0 AT atomice DOT net>
Organization: JSDM Services Ltd
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

On Fri, 26 Jul 2002 21:48:32 +0100
"Chris January" <chris AT atomice DOT net> wrote:

> > > > > but I'm running 1.3.12?
> > > > >
> > > > > Isn't that recent enough?
> > > >
> > > > Don't know.  I'm running 1.3.12-2 and I know it's there.
> > > >
> > > > $ ls /proc/
> > > > 1540  1808  2536  2616  2660  2684  2848     meminfo   stat    version
> > > > 1764  2444  2592  2636  2680  2712  loadavg  registry  uptime
> > > >
> > > > J.
> > > >
> > > Don't get me wrong../proc exists and looks very similar to yours,
> > > but I get that error (i.e. the complaint that /proc is not
> > > mounted) whenever I run top.
> Make sure you are using 1.3.12-2 and not 1.3.12-1 in which the /proc
> filesystem is hopelessly broken.
> 
> Chris
Looks like another download then ;)

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/