public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: 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 09:33:24 +0100	[thread overview]
Message-ID: <c11731a1-7c95-d026-e460-3c35be598cd7@gmail.com> (raw)
In-Reply-To: <CAEhDDbDP4VmRb+dFhtn00RsNrUihdzPO2Zo5tMKL3abk0raajA@mail.gmail.com>

On 21.12.2021 08:54, Csaba Raduly 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
> 

and cygcheck is your friend to find the proper package:

$ cygcheck -p usr/bin/pkill
Found 7 matches for usr/bin/pkill
procps-ng-debuginfo-3.3.15-1 - ...
procps-ng-3.3.15-1 - procps-ng: System and process monitoring utilities
procps-ng-3.3.16-1 - procps-ng: System and process monitoring utilities
procps-ng-3.3.17-1 - procps-ng: System and process monitoring utilities
procps-3.2.8-5 - procps: System and process monitoring utilities ..

PS: procps-ng replaced procps



  reply	other threads:[~2021-12-21  8:33 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 [this message]
2021-12-21 16:20   ` Ken Lobb

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=c11731a1-7c95-d026-e460-3c35be598cd7@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.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).