Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!amgraf!brian386!news
From: news@brian386.UUCP (Wm. Brian McCane)
Newsgroups: comp.unix.wizards
Subject: Re: uucp killing
Message-ID: <427@brian386.UUCP>
Date: 6 Apr 89 18:41:46 GMT
References: <17183@cisunx.UUCP> <809@twwells.uucp>
Reply-To: news@brian386.UUCP (Wm. Brian McCane)
Organization: Harmon Electronics, Inc  Grain Valley, MO
Lines: 32

In article <809@twwells.uucp> bill@twwells.UUCP (T. William Wells) writes:
=In article <17183@cisunx.UUCP> jcbst3@unix.cis.pittsburgh.edu (James C. Benz) writes:
=> For my peace of mind, is there some way to kill all spooled jobs for a given
=> machine queued for uucp?  Let me put that a little more clearly.  Suppose
=> I have a machine foobar, and I have ten jobs queued for uucp to foobar.
=> Foobar has just been relegated to the scrap heap, so these jobs will never
=> get sent, or maybe I just discovered an error in the list of files that I
=> sent to foobar.
=
=There's nothing wrong with going into the spool directory and
=deleting the files contained there. For HDB this is easy, just do rm
=-fr /usr/spool/uucp/foobar, if you are feeling confident.  For the
=old UUCP, I'm not sure exactly how the files are named, but the
=principle is the same: just remove the appropriate files.
=

Why not use a script like :

for i in `uustat -a | awk ' $4 == "foobar" { print $1 } '`
do
	uustat -k $i
done

	brian

(Yeah, I use Bourne Shell, what of it! ;-)

-- 
Wm. Brian McCane                    | Life is full of doors that won't open
                                    | when you knock, equally spaced amid
Disclaimer: I don't think they even | those that open when you don't want
            admit I work here.      | them to. - Roger Zelazny "Blood of Amber"