| 1 |
On Fri, Feb 05, 2021 at 06:55:12AM -0500, Rich Freeman wrote |
| 2 |
> On Fri, Feb 5, 2021 at 2:45 AM Walter Dnes <waltdnes@××××××××.org> wrote: |
| 3 |
> > |
| 4 |
> > So far, so good, but running "ps -ef | grep whatever" and then |
| 5 |
> > typing the kill -SIGSTOP/SIGCONT command on the correct pid is grunt |
| 6 |
> > work, subject to typos. |
| 7 |
> |
| 8 |
> man killall |
| 9 |
|
| 10 |
My reading of the "killall" man page is that it works on command |
| 11 |
names. For my script, "pstop palemoon" stops all instances of Pale |
| 12 |
Moon. But my script greps the entire line, so "pstop slashdot" will |
| 13 |
stop the process... |
| 14 |
|
| 15 |
/home/waltdnes/pm/palemoon/palemoon -new-instance -p slasdot |
| 16 |
|
| 17 |
Does "killall" have that ability to stop a process based on any |
| 18 |
parameters in the command line? |
| 19 |
|
| 20 |
-- |
| 21 |
Walter Dnes <waltdnes@××××××××.org> |
| 22 |
I don't run "desktop environments"; I run useful applications |
Archives