killall process not found

codywohlers · 10-28-2018, 02:02 AM

why can't `killall` find `gpg-agent` process?

Code:

codyw@cody-macbook:~$ ps -ef |grep gpg-agent
codyw      364   300  0 01:01 pts/4    00:00:00 grep --color gpg-agent
codyw    17519     1  0 00:36 ?        00:00:00 gpg-agent --homedir /home/codyw/.gnupg --use-standard-socket --daemon

codyw@cody-macbook:~$ killall gpg-agent
gpg-agent: no process found
returned 1

codyw@cody-macbook:~$ ps -ef |grep gpg-agent
codyw      455   300  0 01:01 pts/4    00:00:00 grep --color gpg-agent
codyw    17519     1  0 00:36 ?        00:00:00 gpg-agent --homedir /home/codyw/.gnupg --use-standard-socket --daemon

MadeInGermany · 10-28-2018, 06:33 AM

A command might alter its arg0 that causes an inconsistancy in the naming.
Check different methods with

Code:

ps -e -o fname,cmd,comm,args

codywohlers · 10-28-2018, 05:00 PM

hmmm...

Code:

codyw@cody-macbook:~$ ps -e -o fname,cmd,comm,args |grep gpg
grep     grep --color gpg            grep            grep --color gpg
gpg-agen gpg-agent --homedir /home/c gpg-agent       gpg-agent --homedir /home/codyw/.gnupg --use-standard-socket --daemon

frankbell · 10-28-2018, 07:27 PM

What happens when you try this?

Code:

$ kill [process number]

MadeInGermany · 10-28-2018, 07:45 PM

Perhaps killall takes the method that corresponds to fname and apparently truncates to 8 characters?
Then it's

Code:

killall gpg-agen

BW-userx · 10-28-2018, 08:50 PM

gpg-agent --homedir /home/codyw/.gnupg --use-standard-socket --daemon

that is the entire process. is it not?

killall "gpg-agent --homedir /home/codyw/.gnupg --use-standard-socket --daemon"
and you only got one, so killall is over kill.

pkill [program name]
https://linux.die.net/man/1/pkill
is another one.

codywohlers · 10-28-2018, 08:57 PM

tried `killall gpg-agen` and it also says process not found. I can tab-complete after killall and get gpg-agent so it knows it's a process.

`kill [process num]` does work.

some info:

Code:

$ killall --version
killall (PSmisc) 23.1

$ lsb_release -sdc; uname -sri
KDE neon LTS User Edition 5.12
bionic
Linux 4.15.0-36-generic x86_64

frankbell · 10-28-2018, 09:02 PM

Quote:

`kill [process num]` does work.

That leads me to theorize that there's something screwy with the process name as reported, but I have no idea what it might be.

Aside: Woo-Hoo. As a friend of mine once said, even a blind pig finds an acorn once and awhile.

BW-userx · 10-28-2018, 09:09 PM

Quote:

Originally Posted by codywohlers

tried `killall gpg-agen` and it also says process not found. I can tab-complete after killall and get gpg-agent so it knows it's a process.

`kill [process num]` does work.

some info:

Code:

$ killall --version
killall (PSmisc) 23.1

$ lsb_release -sdc; uname -sri
KDE neon LTS User Edition 5.12
bionic
Linux 4.15.0-36-generic x86_64

try

Code:

 ps -e -o fname,cmd,comm,args |grep gpg

to get the running one, then copy the entire line between quotes.
gpg-agent is not the process it is only part of it,

Code:

killall "gpg-agent --homedir /home/codyw/.gnupg --use-standard-socket --daemon"

see what that tells ya.

codywohlers · 10-29-2018, 06:59 PM

also tried with no avail:

Code:

codyw@cody-macbook:~$ ps -e -o fname,cmd,comm,args |grep gpg
gpg-agen gpg-agent --homedir /home/c gpg-agent       gpg-agent --homedir /home/codyw/.gnupg --use-standard-socket --daemon
grep     grep --color gpg            grep            grep --color gpg

codyw@cody-macbook:~$ killall "gpg-agent --homedir /home/codyw/.gnupg --use-standard-socket --daemon"
gpg-agent --homedir /home/codyw/.gnupg --use-standard-socket --daemon: No such file or directory
returned 1

codyw@cody-macbook:~$ killall 'gpg-agent --homedir /home/codyw/.gnupg --use-standard-socket --daemon'
gpg-agent --homedir /home/codyw/.gnupg --use-standard-socket --daemon: No such file or directory
returned 1

I've only ever experienced this with gpg-agent

MadeInGermany · 10-30-2018, 02:30 PM

Try pkill instead.
The good thing about pkill is that you can test with pgrep before.
You can augment with -f to search in args, or "-u user" to search for a specific user (process owner) only.
Examples with pgrep:

Code:

pgrep -f "gpg-agent --homedir /home/codyw/.gnupg --use-standard-socket --daemon"
pgrep pgp-agent
pgrep pgp-agen
pgrep -u $USER pgp-agent

Note that pgrep/pkill use regular expressions. E.g. the dot in .gnupg means any character (not just dot).

scasey · 10-30-2018, 02:55 PM

killall also has a regexp option:

Code:

-r, --regexp
              Interpret process name pattern as an extended regular expression

codywohlers · 11-09-2018, 05:52 AM

pkill does work. strange.

Code:

pkill gpg-agent

I also tried killall -r gpg-agent but that still does not work. I'll confirm this behavior on a stock vm and then I guess I'll file a bug with killall.

scasey · 11-09-2018, 12:25 PM

Quote:

Originally Posted by codywohlers

tried `killall gpg-agen` and it also says process not found. I can tab-complete after killall and get gpg-agent so it knows it's a process.

Tab complete only works because there's a file in your $PATH with that name.
It has nothing to do with whether or not it's running or is a process.

mltvsk1 · 11-09-2018, 02:14 PM

Why do you need him so badly?