From: "Henry S. Thompson" <ht@inf.ed.ac.uk>
To: J M <cesarjorgemartinez@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Help with use of pgrep or pkill commands with full name options
Date: Sat, 23 Mar 2024 13:05:58 +0000 [thread overview]
Message-ID: <f5bbk75w11l.fsf@ecclerig.inf.ed.ac.uk> (raw)
In-Reply-To: <CAL8MddXSDRFq4kdHRZdzsURr7eG7rS9A=XrcjxM=znALgN06_Q@mail.gmail.com> (J. M. via Cygwin's message of "Fri\, 22 Mar 2024 16\:56\:27 +0100")
J M via Cygwin writes:
> Help with use of pgrep or pkill commands with full name options.
>
> I trying to use pgrep or pkill utility commands to find processes but using
> the full path names, by example, find /usr/bin/bash (package procps-ng):
>
> Then, if I use pgrep -f /usr/bin/bash, don't find nothing.
I note that on Cygwin:
pgrep -f /bin/bash
finds some but not all of my running bash processes.
pgrep -a bash
finds all of them.
I leave it to others to explain why /usr/bin/bash doesn't work.
I note that on (Debian) Linux the results of the above alternatives
_also_ differ, but that pgrep -f /usr/bin/bash and pgrep -f /bin/bash
both work and give the same results.
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND
e-mail: ht@inf.ed.ac.uk
URL: https://www.ltg.ed.ac.uk/~ht/
[mail from me _always_ has a .sig like this -- mail without it is forged spam]
prev parent reply other threads:[~2024-03-23 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 15:56 J M
2024-03-22 16:22 ` Brian Inglis
2024-03-22 16:41 ` Eliot Moss
2024-03-23 13:05 ` Henry S. Thompson [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=f5bbk75w11l.fsf@ecclerig.inf.ed.ac.uk \
--to=ht@inf.ed.ac.uk \
--cc=cesarjorgemartinez@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).