| 1 |
On Saturday, February 6, 2021 6:07:39 A.M. AEDT Walter Dnes wrote: |
| 2 |
> On Fri, Feb 05, 2021 at 06:55:12AM -0500, Rich Freeman wrote |
| 3 |
> |
| 4 |
> > On Fri, Feb 5, 2021 at 2:45 AM Walter Dnes <waltdnes@××××××××.org> wrote: |
| 5 |
> > > So far, so good, but running "ps -ef | grep whatever" and then |
| 6 |
> > > |
| 7 |
> > > typing the kill -SIGSTOP/SIGCONT command on the correct pid is grunt |
| 8 |
> > > work, subject to typos. |
| 9 |
> > |
| 10 |
> > man killall |
| 11 |
> |
| 12 |
> My reading of the "killall" man page is that it works on command |
| 13 |
> names. For my script, "pstop palemoon" stops all instances of Pale |
| 14 |
> Moon. But my script greps the entire line, so "pstop slashdot" will |
| 15 |
> stop the process... |
| 16 |
> |
| 17 |
> /home/waltdnes/pm/palemoon/palemoon -new-instance -p slasdot |
| 18 |
> |
| 19 |
> Does "killall" have that ability to stop a process based on any |
| 20 |
> parameters in the command line? |
| 21 |
|
| 22 |
|
| 23 |
Someone else mentioned pgrep. It has an associated pkill command as well. |
| 24 |
Both appear to have a "-f" option to also search on the full command line. |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/ |
| 29 |
Asking for technical help in newsgroups? Read this first: |
| 30 |
http://catb.org/~esr/faqs/smart-questions.html#intro |
Archives