Date: Sat, 27 May 2000 16:46:26 +0100 From: Brian Somers <brian@Awfulhak.org> To: John Baldwin <jhb@FreeBSD.org> Cc: Randall Hopper <aa8vb@nc.rr.com>, stable@FreeBSD.org, housley@thehousleys.net, brian@hak.lan.Awfulhak.org Subject: Re: killall question Message-ID: <200005271546.QAA64909@hak.lan.Awfulhak.org> In-Reply-To: Message from John Baldwin <jhb@FreeBSD.org> of "Sat, 27 May 2000 10:49:20 EDT." <20000527144920.WNSL22611.mail.rdc1.va.home.com@john.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
>
> On 27-May-00 Randall Hopper wrote:
> > housley@thehousleys.net:
> > |Randall Hopper <aa8vb@nc.rr.com> said:
> > |
> > |> I have a script I run named "newroot". I want to kill it with killall.
> > |>
> > |> > ps -ax | grep newroot
> > |> 842 1 rhh /bin/sh /home/rhh/bin/newroot 360
> > |>
> > |You will have to do something like
> > |
> > |kill `ps -ax | grep newroot | sed -e '^[0-9]*'`
> >
> > Ok. I thought I'd at least try to use the system version, but sounds like
> > it's just not as flexible as killall's on other systems.
> >
> > Here's the shell script I settled on to override the default /usr/bin/killall:
> >
> > ps -x | grep "$1" | egrep -v "grep|$0" | awk '{print $1;}'
>
> % killall grep
# killall grepscript
There are bad sub-string implications there too....
--
Brian <brian@Awfulhak.org> <brian@[uk.]FreeBSD.org>
<http://www.Awfulhak.org>; <brian@[uk.]OpenBSD.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005271546.QAA64909>