Help with use of pgrep or pkill commands with full name options

Help with use of pgrep or pkill commands with full name options

[J M]

[-- Attachment #1: Type: text/plain, Size: 436 bytes --]

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.

Using pkill -f /usr/bin/bash don't get the task.

If I use pidof /usr/bin/bash, this works.

How do I get it to do use pgrep, pkill, etc?

Regards,
Cesar Jorge

Re: Help with use of pgrep or pkill commands with full name options

[Brian Inglis]

On 2024-03-22 09:56, J M via Cygwin wrote:
> 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.
> 
> Using pkill -f /usr/bin/bash don't get the task.
> 
> If I use pidof /usr/bin/bash, this works.
> 
> How do I get it to do use pgrep, pkill, etc?

Look at the proc names using `procps -ae` - if it does not show a path, do not 
use `-f, --fullname /path/name`, just use `name`, and you may have to experiment 
if you want to use `-x, --exact`, and possibly other options.

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

Re: Help with use of pgrep or pkill commands with full name options

[Eliot Moss]

On 3/22/2024 11:56 AM, J M via Cygwin wrote:
> 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.
> 
> Using pkill -f /usr/bin/bash don't get the task.
> 
> If I use pidof /usr/bin/bash, this works.
> 
> How do I get it to do use pgrep, pkill, etc?

Seems to use the name without the full path, e.g.,
bash as opposed to /bin/bash, etc.  Not sure why ...

EM

Re: Help with use of pgrep or pkill commands with full name options

[Henry S. Thompson]

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]