Human data entry is the top cause of erorr. A small script can
allieviate this problem. Something as simple as ..
ps ux | grep "process name" | \
grep -v grep | \
awk ' { print $2 } ' | \
xargs kill -9
Throw that into a script that takes process name as the arguement, and
modify ps options as needed.
/vijay
On Fri, 26 Nov 2004, Eben King wrote:
> On Sat, 13 Nov 2004, Christopher Hotchkiss wrote:
>
> > > Up arrow, edit, enter, until you get it right. I often misread numbers,
> > > which is especially bad when I run 'ps' or 'top' and find that 12345 is
> > > the process to kill, so I do it, and nothing (obvious) happens so I
> > > re-read and its actual PID is 12354. Oops. (What did I kill instead?)
> > > So typoes aren't a "newbie" thing necessarily.
> > >
> > This is an easy fix, 'killall' + the process name. So to kill mplayer,
> > type 'killall mplayer.'
> > Be careful that you dont have multiple instances running though!
>
> Yeah, but what if I want to go away is "vi .bashrc" but I want to keep "vi
> .login"? Also, scripts are listed as "/bin/ksh /export/bin/logmonitor"
> (or whatever), which makes them hard to kill by name, but easy (modulo
> misreading) by PID. It's easier to find the PID than to check for
> uniqueness of the executable's name. And don't use killall in another OS
> without checking its man page first; Linux's definition of "killall" is
> ... odd.
>
>
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 18:30:24 EDT