public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Lobb <klobb42655@gmail.com>
To: Csaba Raduly <rcsaba@gmail.com>
Cc: cygwin list <cygwin@cygwin.com>
Subject: Re: libprocps8 and missing free, prockill, pkill, pgrep, pmap, procps, tload, top, uptime, vmstat, w, and watch
Date: Tue, 21 Dec 2021 11:20:36 -0500	[thread overview]
Message-ID: <CAN-PN0RLu50c-yq4fqOt3uFaxbazXJXcNyUUBEXprSCcKSQ2cg@mail.gmail.com> (raw)
In-Reply-To: <CAEhDDbDP4VmRb+dFhtn00RsNrUihdzPO2Zo5tMKL3abk0raajA@mail.gmail.com>

Great, thank you -- just what I needed to know.
Works fine now.

Thank you,
Kenneth Lobb

On Tue, Dec 21, 2021 at 2:55 AM Csaba Raduly <rcsaba@gmail.com> wrote:

> Hi Ken,
>
> On Mon, 20 Dec 2021 at 18:02, Ken Lobb  wrote:
> >
> > I'm probably missing something that needs to be configured, but I'm
> trying
> > to utilize uptime & vmstat and other performance/load utilities in
> Cygwin.
> > I installed the libprocps8 package, but none of these utilities can be
> > found.
>
> libprocps8 (
> https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Flibprocps8%2Flibprocps8-3.3.17-1&grep=libprocps8
> )
> contains only a DLL (as its name suggests).
>
> As Ken Brown wrote, you need
>
> https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Fprocps-ng%2Fprocps-ng-3.3.17-1&grep=procps-ng
>
> --
> You can get very substantial performance improvements
> by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
> So if you're looking for a completely portable, 100% standards-conformant
> way
> to get the wrong information: this is what you want. - Scott Meyers
> (C++TDaWYK)
>

      parent reply	other threads:[~2021-12-21 16:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-20 17:02 Ken Lobb
2021-12-20 17:49 ` Ken Brown
2021-12-21  7:54 ` Csaba Raduly
2021-12-21  8:33   ` Marco Atzeri
2021-12-21 16:20   ` Ken Lobb [this message]

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=CAN-PN0RLu50c-yq4fqOt3uFaxbazXJXcNyUUBEXprSCcKSQ2cg@mail.gmail.com \
    --to=klobb42655@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=rcsaba@gmail.com \
    /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).