public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "John Morrison" <john.r.morrison@ntlworld.com>
To: "Jim George" <jim.george@blueyonder.co.uk>, <cygwin@cygwin.com>
Subject: RE: a way to read the current cpu load from the shell or via a  cmdline utility in cygwin?
Date: Fri, 26 Jul 2002 07:40:00 -0000	[thread overview]
Message-ID: <NCEBJJFMCAOKNNABBFIMOEPMCDAA.john.r.morrison@ntlworld.com> (raw)
In-Reply-To: <20020726124225.5a789886.jim.george@blueyonder.co.uk>

> on Behalf Of Jim George
> 
> On Fri, 26 Jul 2002 11:15:19 +0100
> "John Morrison" <john.r.morrison@ntlworld.com> 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.

Oh, sorry, missread.  I don't think I can help then :(

J.

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

  reply	other threads:[~2002-07-26 11:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-24  5:59 Dylan Cuthbert
2002-07-24  6:32 ` Gunnar Norling
2002-07-24  6:45 ` John Morrison
2002-07-25  1:57   ` Jim George
2002-07-25  6:01     ` Igor Pechtchanski
2002-07-25  8:54       ` Tony Arnold
2002-07-25 10:01         ` Igor Pechtchanski
2002-07-26 15:24         ` Chris January
2002-07-26 17:54           ` Christopher Faylor
2002-07-26 17:58             ` Chris January
2002-07-25  8:55       ` Greg McCrory
2002-07-25 13:37         ` Igor Pechtchanski
2002-07-26  1:35           ` Dylan Cuthbert
2002-07-26  6:30           ` Jim George
     [not found]             ` <OIENKAGCMBEDKDHGANIKKEONCGAA.john.r.morrison@ntlworld.com>
2002-07-26  6:57               ` Jim George
2002-07-26  7:17                 ` John Morrison
2002-07-26  7:39                   ` Jim George
2002-07-26  7:40                     ` John Morrison [this message]
2002-07-26 16:35                       ` Chris January
2002-07-27  7:05                         ` Jim George
2002-07-26 14:22                     ` Chris January
2002-07-26 19:06                       ` Jim George
2002-07-26 19:33                         ` Chris January
2002-07-26 13:15             ` Igor Pechtchanski
2002-07-26 18:31               ` Jim George
2002-07-26 18:47                 ` Igor Pechtchanski
2002-07-27  7:00                   ` Jim George
2002-07-27  8:45                     ` Chris January
2002-07-27 19:55                     ` Igor Pechtchanski
2002-07-26 13:48 ` Chris January
2002-07-27  6:26   ` Dylan Cuthbert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=NCEBJJFMCAOKNNABBFIMOEPMCDAA.john.r.morrison@ntlworld.com \
    --to=john.r.morrison@ntlworld.com \
    --cc=cygwin@cygwin.com \
    --cc=jim.george@blueyonder.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).