On Saturday, February 6, 2021 6:07:39 A.M. AEDT Walter Dnes wrote:
> On Fri, Feb 05, 2021 at 06:55:12AM -0500, Rich Freeman wrote
>
> > On Fri, Feb 5, 2021 at 2:45 AM Walter Dnes wrote:
> > > So far, so good, but running "ps -ef | grep whatever" and then
> > >
> > > typing the kill
On Fri, Feb 05, 2021 at 04:42:26PM -0600, Matt Connell (Gmail) wrote
> On Fri, 2021-02-05 at 13:24 -0500, Walter Dnes wrote:
> > I'll have to take that back. It happened again, and I was not
> > fiddling with pstop/pcont. The common element seems to be that I was
> > compiling Pale Moon 29.0
Hello,
On Fri, 05 Feb 2021, Walter Dnes wrote:
>On Fri, Feb 05, 2021 at 06:55:12AM -0500, Rich Freeman wrote
>> On Fri, Feb 5, 2021 at 2:45 AM Walter Dnes wrote:
>> > So far, so good, but running "ps -ef | grep whatever" and then
>> > typing the kill -SIGSTOP/SIGCONT command on the correct pid
On Fri, 2021-02-05 at 13:24 -0500, Walter Dnes wrote:
> I'll have to take that back. It happened again, and I was not
> fiddling with pstop/pcont. The common element seems to be that I was
> compiling Pale Moon 29.0 each time it crashed. A machine with 8 gigs of
> ram, and 598 of 905 gigs
On Fri, Feb 05, 2021 at 02:00:05PM -0500, Walter Dnes wrote
>
> In the course of experimentation, I've made versions that killed
> critical processes, requiring a reboot. {ALT}{SYSRQ} to the rescue .
> I'll stick with stuff that works.
I'll have to take that back. It happened again, and I
On Fri, 5 Feb 2021 14:07:39 -0500, Walter Dnes wrote:
> > man killall
>
> My reading of the "killall" man page is that it works on command
> names. For my script, "pstop palemoon" stops all instances of Pale
> Moon. But my script greps the entire line, so "pstop slashdot" will
> stop the
On Fri, Feb 5, 2021 at 2:07 PM Walter Dnes wrote:
>
> On Fri, Feb 05, 2021 at 06:55:12AM -0500, Rich Freeman wrote
> > On Fri, Feb 5, 2021 at 2:45 AM Walter Dnes wrote:
> > >
> > > So far, so good, but running "ps -ef | grep whatever" and then
> > > typing the kill -SIGSTOP/SIGCONT command on
On Fri, Feb 05, 2021 at 06:55:12AM -0500, Rich Freeman wrote
> On Fri, Feb 5, 2021 at 2:45 AM Walter Dnes wrote:
> >
> > So far, so good, but running "ps -ef | grep whatever" and then
> > typing the kill -SIGSTOP/SIGCONT command on the correct pid is grunt
> > work, subject to typos.
>
> man
On Fri, Feb 05, 2021 at 03:46:45AM -0500, Andrew Udvare wrote
>
> > On 2021-02-05, at 02:45, Walter Dnes wrote:
> >
> > done < /dev/shm/temp.txt
>
> You don't need to write a temporary file. You can pipe this directly into the
> while loop:
>
> while read
> do
> ...
> done < <(ps -ef | grep
Awesome stuff!
It might be unrelated, but I would like to mention a script[1] here,
which I have written in Bash to analyse process signals. It is called
"psig", which mimics some of the behaviour of Solaris' "psig" binary:
$ psig 23024
PID: 23024
Name: chrome
Queued: 0/63858
On Fri, Feb 5, 2021 at 2:45 AM Walter Dnes wrote:
>
> So far, so good, but running "ps -ef | grep whatever" and then
> typing the kill -SIGSTOP/SIGCONT command on the correct pid is grunt
> work, subject to typos.
man killall
--
Rich
> On 2021-02-05, at 02:45, Walter Dnes wrote:
>
> done < /dev/shm/temp.txt
You don't need to write a temporary file. You can pipe this directly into the
while loop:
while read
do
...
done < <(ps -ef | grep ${1} | grep -v "grep ${1}" | grep -v pstop)
Also to avoid the second grep in Bash at
Thanks for all the help over the years fellow Gentoo'ers. Maybe I can
return the favour. So you've got a bunch of programs like Gnumeric or
QEMU or Pale Moon ( or Firefox or Chrome or Opera ) sessions open, that
are chewing up cpu and ram. You need those resouces for another
program, but you
13 matches
Mail list logo
