denbeste@bbn.com (Steven Den Beste) (08/02/89)
Today we received a large number of news articles dated July 22, which we have received before. I located 50 or so of them and analyzed the paths by which they arrived here. The earliest site that they all have in common is 'sunybcs'. Before that, most of the articles came from 'rutgers', but some came from 'boulder' and I found one which came from 'bingvaxu'. By the way, the articles I checked took several paths from 'sunybcs' to here. I didn't look very hard to find those articles - maybe 8 newsgroups. I can only conclude that several hundred such articles were delivered.
scs@itivax.iti.org (Steve Simmons) (08/03/89)
We've starting seeing the same here. A little brute-force grepping determined all the articles involved were posted July 22 with the sites you mentioned. They comprised about 15% of the articles received in the last 24 hours. -- Steve Simmons scs@vax3.iti.org Industrial Technology Institute Ann Arbor, MI. "Velveeta -- the Spam of Cheeses!" -- Uncle Bonsai
emv@math.lsa.umich.edu (Edward Vielmetti) (08/03/89)
To wipe out all of the old news with rn the following macro was useful: &&( /22 Jul/h:j Something about reading old news gives me a headache, especially to see old lame arguments get repeated over and over. (For that matter some of the new news isn't much better....)
chip@vector.Dallas.TX.US (Chip Rosenthal) (08/03/89)
In article <43675@bbn.COM> denbeste@BBN.COM (Steven Den Beste) writes: >By the way, the articles I checked took several paths from 'sunybcs' to here. >I didn't look very hard to find those articles - maybe 8 newsgroups. I can >only conclude that several hundred such articles were delivered. I went through the entire comp.all heirarchy here looking for messages with "!sunybcs!" in the Path dated July 22nd. I came up with *325* messages. Attached below is a shar archive with: (1) the message-id's from these 325 articles, and (2) a script to read message-id's from the standard input and cancel them locally. If you want to zap these messages, run: sh do-cancel < bogus-mssgid P.S. To whoever did this -- thanks a lot. You blew out the space on my /local/spool filesystem. --- cut here ----------------------------------------------------------------- #! /bin/sh # this is a "shar" archive - run through "/bin/sh" to extract 2 files: # do-cancel bogus-mssgid # Wrapped by chip@vector on Wed Aug 2 19:08:18 CDT 1989 # Unpacking this archive requires: sed test wc (possibly mkdir) # Existing files will not be clobbered unless "-c" is specified on the cmd line. if test -f do-cancel -a "$1" != "-c" ; then echo "do-cancel: file exists - will not be overwritten" else echo "x - do-cancel (file 1 of 2, 255 chars)" sed -e 's/^X//' << 'END_OF_FILE_do-cancel' > do-cancel X: X XINEWS=/local/lib/news/inews X Xwhile read mssgid ; do X X echo "cancelling $mssgid..." X X $INEWS -h <<- END-OF-CANCEL-MSSG X Subject: cancel X Control: cancel $mssgid X Newsgroups: control X Distribution: local X X cleaning up... X END-OF-CANCEL-MSSG X Xdone END_OF_FILE_do-cancel size="`wc -c < do-cancel`" if test 255 -ne "$size" ; then echo "do-cancel: extraction error - got $size chars" fi fi if test -f bogus-mssgid -a "$1" != "-c" ; then echo "bogus-mssgid: file exists - will not be overwritten" else echo "x - bogus-mssgid (file 2 of 2, 8174 chars)" sed -e 's/^X//' << 'END_OF_FILE_bogus-mssgid' > bogus-mssgid X<0Yahsbi00Xoe00qp0Y@andrew.cmu.edu> X<1023@aber-cs.UUCP> X<10294@claris.com> X<1036@taurus.BITNET> X<10417@smoke.BRL.MIL> X<10930@ibmpcug.UUCP> X<10931@ibmpcug.UUCP> X<1093@syma.sussex.ac.uk> X<11065@cit-vax.Caltech.Edu> X<11069@cit-vax.Caltech.Edu> X<11071@cit-vax.Caltech.Edu> X<11078@nuchat.UUCP> X<110882@sun.Eng.Sun.COM> X<110883@sun.Eng.Sun.COM> X<110884@sun.Eng.Sun.COM> X<110885@sun.Eng.Sun.COM> X<111700106@uxa.cso.uiuc.edu> X<113300084@uxa.cso.uiuc.edu> X<1133@vsi.COM> X<1134@vsi.COM> X<113@accsys.acc.uu.no> X<115200034@uxa.cso.uiuc.edu> X<117@accsys.acc.uu.no> X<118@scooter.UUCP> X<11910002@hpldola.HP.COM> X<1201@draken.nada.kth.se> X<12027@eddie.MIT.EDU> X<12029@eddie.MIT.EDU> X<1202@draken.nada.kth.se> X<12057@bloom-beacon.MIT.EDU> X<12060@bloom-beacon.MIT.EDU> X<1210@masscomp.UUCP> X<1221@bnlux0.bnl.gov> X<12230@well.UUCP> X<12231@well.UUCP> X<12250@well.UUCP> X<1242@psuhcx.psu.edu> X<12502969081.13.NEUMANN@KL.SRI.COM> X<125@avatar.UUCP> X<1268@lad.UUCP> X<1290@cbnewsc.ATT.COM> X<1291@cbnewsc.ATT.COM> X<1313@inria.inria.fr> X<1349@novavax.UUCP> X<1388@ruuinf.cs.ruu.nl> X<14231@ut-emx.UUCP> X<14404@bfmny0.UUCP> X<14547@watdragon.waterloo.edu> X<14562@watdragon.waterloo.edu> X<146@cerc.wvu.wvnet.edu.edu> X<1471@pfm.UUCP> X<14737@pasteur.Berkeley.EDU> X<14738@pasteur.Berkeley.EDU> X<14752@pasteur.Berkeley.EDU> X<1479@bucket.UUCP> X<147@cerc.wvu.wvnet.edu.edu> X<1480@bucket.UUCP> X<1518@netcom.UUCP> X<1520@cs-spool.calgary.UUCP> X<1520@frog.UUCP> X<1521@frog.UUCP> X<1523@cbnewsh.ATT.COM> X<1526@stl.stc.co.uk> X<1527@stl.stc.co.uk> X<1528@stl.stc.co.uk> X<1547@agora.UUCP> X<1591@munnari.oz.au> X<1592@munnari.oz.au> X<159@unmvax.unm.edu> X<16233.8906161458@np1a.bristol.ac.uk> X<1634@petsd.UUCP> X<1650@murdu.oz> X<1675@itivax.iti.org> X<16813@gryphon.COM> X<177@quad.uucp> X<17914@usc.edu> X<17@minya.UUCP> X<18110@paris.ics.uci.edu> X<18116@paris.ics.uci.edu> X<18218.8906161357@vanuata.cs.glasgow.ac.uk> X<185@orac.pgh.pa.us> X<18600015@uxh.cso.uiuc.edu> X<18@minya.UUCP> X<195300008@trsvax> X<19551@cup.portal.com> X<19553@cup.portal.com> X<19558@cup.portal.com> X<19559@cup.portal.com> X<19560@cup.portal.com> X<19575@cup.portal.com> X<19578@cup.portal.com> X<19596@cup.portal.com> X<1989Jun17.081153.19335@ziebmef.uucp> X<1989Jun17.160424.7086@marob.masa.com> X<1989Jun18.052245.11340@twwells.com> X<1989Jun18.114923.11903@csusac.uucp> X<1989Jun18.120806.4353@comp.vuw.ac.nz> X<1989Jun18.154711.14602@twwells.com> X<1RqFNj#4WSMzl=ggw@wolves.uucp> X<2206@bingvaxu.cc.binghamton.edu> X<2209@bingvaxu.cc.binghamton.edu> X<22256@iuvax.cs.indiana.edu> X<2225@trantor.harris-atd.com> X<2226@drilex.UUCP> X<2228@vicom.COM> X<224@bilver.UUCP> X<2378@etive.ed.ac.uk> X<2379@etive.ed.ac.uk> X<2383@etive.ed.ac.uk> X<2401@yunexus.UUCP> X<240@cbnewsd.ATT.COM> X<245300016@uxe.cso.uiuc.edu> X<2454@blake.acs.washington.edu> X<246300004@uxa.cso.uiuc.edu> X<246400012@uxa.cso.uiuc.edu> X<25566@agate.BERKELEY.EDU> X<25581@agate.BERKELEY.EDU> X<25588@agate.BERKELEY.EDU> X<259@nlgvax.UUCP> X<26000@amdcad.AMD.COM> X<2600@cveg.uucp> X<2601@cveg.uucp> X<2602@cveg.uucp> X<26@nx32s.anduk.co.uk> X<27059@lll-winken.LLNL.GOV> X<27192@watmath.waterloo.edu> X<2739@ndsuvax.UUCP> X<2740@ndsuvax.UUCP> X<2741@ndsuvax.UUCP> X<2752@maccs.McMaster.CA> X<2777@kappl.cs.vu.nl> X<281@ecijmm.UUCP> X<296@ucl-cs.UUCP> X<297@ucl-cs.UUCP> X<2982@csd4.milw.wisc.edu> X<2996@rtech.rtech.com> X<300@mipos3.intel.com> X<302@denwa.uucp> X<3030@portia.Stanford.EDU> X<3055.8906181203@paama.cs.glasgow.ac.uk> X<312@ohs.UUCP> X<313@ohs.UUCP> X<3159@cayman.COM> X<3183@sun.soe.clarkson.edu> X<3203@buengc.BU.EDU> X<3212@alliant.Alliant.COM> X<3256@ogccse.ogc.edu> X<3261@ogccse.ogc.edu> X<328@larouch.UUCP> X<329@isncr.is.uu.no> X<33254@bu-cs.BU.EDU> X<3341@titcce.cc.titech.JUNET> X<338@celit.UUCP> X<339@celit.UUCP> X<340@rls.UUCP> X<351@ctycal.UUCP> X<3526@lindy.Stanford.EDU> X<359@ceres.physics.uiowa.edu> X<3604@ddsw1.MCS.COM> X<3607@ddsw1.MCS.COM> X<3610@ddsw1.MCS.COM> X<3611@ddsw1.MCS.COM> X<3703@alembic.ACS.COM> X<3898@tank.uchicago.edu> X<391@csv.viccol.edu.au> X<396@moegate.UUCP> X<398@bpdsun1.UUCP> X<4136@uhccux.uhcc.hawaii.edu> X<41594@bbn.COM> X<4217@oregon.uoregon.edu> X<4263@bgsuvax.UUCP> X<430@uwslh.UUCP> X<4404@crash.cts.com> X<4409@crash.cts.com> X<4410@crash.cts.com> X<4411@crash.cts.com> X<4594@ficc.uu.net> X<4596@ficc.uu.net> X<4599@ficc.uu.net> X<463@logicon.arpa> X<47700055@uxe.cso.uiuc.edu> X<494@silence.princeton.nj.us> X<499@wubios.wustl.edu> X<50500132@uxe.cso.uiuc.edu> X<507@limbic.UUCP> X<509@unipas.fmi.uni-passau.de> X<5340005@hpfcdc.HP.COM> X<545@daitc.daitc.mil> X<546@daitc.daitc.mil> X<5533@rpi.edu> X<5534@rpi.edu> X<56193@linus.UUCP> X<56195@linus.UUCP> X<5768@goofy.megatest.UUCP> X<5793@hubcap.clemson.edu> X<5794@hubcap.clemson.edu> X<579@lakart.UUCP> X<580@lakart.UUCP> X<58144@uunet.UU.NET> X<58145@uunet.UU.NET> X<58146@uunet.UU.NET> X<58147@uunet.UU.NET> X<58148@uunet.UU.NET> X<58149@uunet.UU.NET> X<58150@uunet.UU.NET> X<58151@uunet.UU.NET> X<58152@uunet.UU.NET> X<586@astbe.UUCP> X<595@chyde.uwasa.fi> X<597@chyde.uwasa.fi> X<598@chyde.uwasa.fi> X<60@wells.UUCP> X<6197@pdn.paradyne.com> X<6198@pdn.paradyne.com> X<619@tuck.nott-cs.UUCP> X<632@ispi.UUCP> X<636@lzaz.ATT.COM> X<653@lopez.UUCP> X<659@whizz.uucp> X<66000034@uxe.cso.uiuc.edu> X<66000035@uxe.cso.uiuc.edu> X<66000036@uxe.cso.uiuc.edu> X<695@srhqla.UUCP> X<69@enea.se> X<701@galaxia.Newport.RI.US> X<702@oresoft.uu.net> X<707@isaak.UUCP> X<708@isaak.UUCP> X<709@isaak.UUCP> X<711@soleil.UUCP> X<718@pitstop.West.Sun.COM> X<7199@c3pe.UUCP> X<7202@c3pe.UUCP> X<7207@ecsvax.UUCP> X<7209@ecsvax.UUCP> X<725@serene.UUCP> X<728@serene.UUCP> X<739@ecrcvax.UUCP> X<739@lilink.UUCP> X<76*delaneyg@wnre.aecl.cdn> X<7680@spool.cs.wisc.edu> X<779@redsox.bsw.com> X<780@redsox.bsw.com> X<781@cgh.UUCP> X<781@redsox.bsw.com> X<782@cgh.UUCP> X<783@redsox.bsw.com> X<8004@saturn.ucsc.edu> X<8005@saturn.ucsc.edu> X<8006@saturn.ucsc.edu> X<8007@saturn.ucsc.edu> X<8008@saturn.ucsc.edu> X<8009@saturn.ucsc.edu> X<8020019@hp-lsd.HP.COM> X<81398@ti-csl.csc.ti.com> X<81452@ti-csl.csc.ti.com> X<81=g024X36Zp01@amdahl.uts.amdahl.com> X<8204@boring.cwi.nl> X<8388@killer.DALLAS.TX.US> X<8389@killer.DALLAS.TX.US> X<8390@killer.DALLAS.TX.US> X<8391@killer.DALLAS.TX.US> X<8430@techunix.BITNET> X<849@crdgw1.crd.ge.com> X<8542@pyr.gatech.EDU> X<859@hcx1.UUCP> X<8709@chinet.chi.il.us> X<8710@chinet.chi.il.us> X<8714@chinet.chi.il.us> X<8718@chinet.chi.il.us> X<8720@chinet.chi.il.us> X<8906121706.AA14213@parallax.parallax.com> X<8906141456.AA28060@jerry.inria.fr> X<8906141633.AA01919@sunned.sun.com> X<8906141934.AA09132@crdgw1.ge.com> X<8906141943.AA04269@gateway.mitre.org> X<8906142251.AA17376@Hercules.csl.sri.com> X<8906151444.AA29900@interlan.interlan.com> X<8906152338.AA01346@braden.isi.edu> X<8906161221.AA00671@bland.mitre.org> X<890616160621.26401ec2@Luac.Sdsc.Edu> X<890616161123.20a017d2@SIC.Epfl.CH> X<8906162041.AA00487@mashnee.wellfleet.com> X<890617.08274909.017157@SFA.CP6> X<8906171008.AA21507@ucbvax.Berkeley.EDU> X<8906171112.aa26686@SMOKE.BRL.MIL> X<8906171206.AA26983@ucbvax.Berkeley.EDU> X<8906171303.AA29579@ucbvax.Berkeley.EDU> X<8906171411.AA01915@WLV.IMSD.CONTEL.COM> X<8906171751.AA12386@ucbvax.Berkeley.EDU> X<8906171926.aa28625@SMOKE.BRL.MIL> X<8906171935.AA17165@ucbvax.Berkeley.EDU> X<8906172235.AA25320@ucbvax.Berkeley.EDU> X<8906172325.AA02644@sneezy.lanl.gov> X<8906180043.AA10340@cunixd.cc.columbia.edu> X<8906180052.AA20316@obsolete.UUCP> X<8906180114.AA02197@ucbvax.Berkeley.EDU> X<8906180236.AA11889@crash.cts.com> X<8906180438.AA12145@crash.cts.com> X<8906180439.AA12189@crash.cts.com> X<8906180439.AA12193@crash.cts.com> X<8906180440.AA12197@crash.cts.com> X<8906181038.AA14657@crash.cts.com> X<8906181131.AA04345@s4.tau.ac.il> X<8906181137.AA14911@crash.cts.com> X<8906181541.AA25292@mitre.arpa> X<8906182105.AA23067@mahendo.Jpl.Nasa.Gov> X<8936.613766838@cheetah.nyser.net> X<897@orbit.UUCP> X<89Jun17.204724edt.11705@neat.ai.toronto.edu> X<908@prlhp1.prl.philips.co.uk> X<921@tukki.jyu.fi> X<9436@csli.Stanford.EDU> X<9628@j.cc.purdue.edu> X<9968@dasys1.UUCP> X<9975@dasys1.UUCP> X<998@amethyst.math.arizona.edu> X<BOB.89Jun17141354@giza.cis.ohio-state.edu> X<CMM.0.88.614104020.slndstrm@> X<GRUNWALD.89Jun17210544@flute.cs.uiuc.edu> X<Jun.17.10.59.24.1989.25625@aramis.rutgers.edu> X<Jun.18.00.34.37.1989.27194@topaz.rutgers.edu> X<SHIRONO.89Jun17190318@hcx3.ssd.harris.com> X<TED.89Jun17223624@kythera.nmsu.edu> X<WISNER.89Jun17111853@anableps.berkeley.edu> END_OF_FILE_bogus-mssgid size="`wc -c < bogus-mssgid`" if test 8174 -ne "$size" ; then echo "bogus-mssgid: extraction error - got $size chars" fi fi echo "done - 2 files extracted" exit 0 --- cut here ----------------------------------------------------------------- -- Chip Rosenthal / chip@vector.Dallas.TX.US / Dallas Semiconductor / 214-450-5337 "I wish you'd put that starvation box down and go to bed" - Albert Collins' Mom
Makey@LOGICON.ARPA (Jeff Makey) (08/03/89)
To add to the 325 Chip Rosenthal already posted, following are the
message-ids of another 227 articles dated 22 Jul 89 that came through
sunybcs. I found it easier just to delete the files from the news
spool directory rather than to generate hundreds of local cancel
articles for them.
-------------------------- cut here -----------------------------
<1022@aber-cs.UUCP>
<10362@watcgl.waterloo.edu>
<10440002@hpcndaw.HP.COM>
<1089@syma.sussex.ac.uk>
<10910019@hpldola.HP.COM>
<1091@syma.sussex.ac.uk>
<11066@cit-vax.Caltech.Edu>
<11067@cit-vax.Caltech.Edu>
<11078@nuchat.UUCP>
<11078@nuchat.UUCP>
<11078@nuchat.UUCP>
<110883@sun.Eng.Sun.COM>
<110883@sun.Eng.Sun.COM>
<1110009@hpvcfs1.HP.COM>
<1121@sequent.cs.qmc.ac.uk>
<1122@sequent.cs.qmc.ac.uk>
<1181@blackbird.afit.af.mil>
<118@scooter.UUCP>
<12027@eddie.MIT.EDU>
<1202@masscomp.UUCP>
<12237@well.UUCP>
<12245@well.UUCP>
<124@nisca.ircc.ohio-state.edu>
<1276@pkmab.se>
<1288@cbnewsc.ATT.COM>
<1313@inria.inria.fr>
<1354@l.cc.purdue.edu>
<1355@l.cc.purdue.edu>
<1410155@hpcilzb.HP.COM>
<1427@dover.sps.mot.com>
<14555@watdragon.waterloo.edu>
<14555@watdragon.waterloo.edu>
<14791@duke.cs.duke.edu>
<14791@duke.cs.duke.edu>
<1483@bucket.UUCP>
<15187.249A85C2@urchin.fidonet.org>
<1520@frog.UUCP>
<15249.249BD936@urchin.fidonet.org>
<1528@stl.stc.co.uk>
<1546@agora.UUCP>
<1596@munnari.oz.au>
<1597@bute.tcom.stc.co.uk>
<1598@bute.tcom.stc.co.uk>
<1704@sw1e.UUCP>
<1704@sw1e.UUCP>
<17914@usc.edu>
<17914@usc.edu>
<17@loop.UUCP>
<191@m2cs.uu.no>
<192@iclswe.UUCP>
<194@poopsie.UUCP>
<19536@cup.portal.com>
<19546@cup.portal.com>
<19548@cup.portal.com>
<19559@cup.portal.com>
<19589@cup.portal.com>
<19591@cup.portal.com>
<19600@cup.portal.com>
<19613@cup.portal.com>
<196500028@trsvax>
<1989Jun16.222203.354@mdivax1.uucp>
<1989Jun18.154711.14602@twwells.com>
<1989Jun18.154711.14602@twwells.com>
<1989Jun18.154711.14602@twwells.com>
<1989Jun18.154711.14602@twwells.com>
<1989Jun18.154711.14602@twwells.com>
<201500006@cdp>
<209@baird.cs.strath.ac.uk>
<210015@speclab.bgp-usgs.gov>
<214@anasaz.UUCP>
<216@anasaz.UUCP>
<218@anasaz.UUCP>
<2208@bingvaxu.cc.binghamton.edu>
<220@anasaz.UUCP>
<221@anasaz.UUCP>
<22256@iuvax.cs.indiana.edu>
<222@anasaz.UUCP>
<224@bilver.UUCP>
<2260100@hpfelg.HP.COM>
<2293@ccnysci.UUCP>
<2316@amelia.nas.nasa.gov>
<2319@pur-phy>
<2333@uwovax.uwo.ca>
<2338@uwovax.uwo.ca>
<2381@etive.ed.ac.uk>
<238@cbnewsd.ATT.COM>
<2400@yunexus.UUCP>
<2400@yunexus.UUCP>
<240@cbnewsd.ATT.COM>
<240@cbnewsd.ATT.COM>
<2454@blake.acs.washington.edu>
<2455@blake.acs.washington.edu>
<2455@blake.acs.washington.edu>
<24998@shemp.CS.UCLA.EDU>
<25567@agate.BERKELEY.EDU>
<2601@cveg.uucp>
<26900069@m.cs.uiuc.edu>
<298@ucl-cs.UUCP>
<2996@rtech.rtech.com>
<300@mipos3.intel.com>
<312@umigw.MIAMI.EDU>
<312@umigw.MIAMI.EDU>
<3212@alliant.Alliant.COM>
<3212@alliant.Alliant.COM>
<3214@buengc.BU.EDU>
<3218@buengc.BU.EDU>
<3219@buengc.BU.EDU>
<3237@kitty.UUCP>
<3239@kitty.UUCP>
<3244@kitty.UUCP>
<3245@kitty.UUCP>
<3341@titcce.cc.titech.JUNET>
<3341@titcce.cc.titech.JUNET>
<3341@titcce.cc.titech.JUNET>
<339@celit.UUCP>
<3456@cps3xx.UUCP>
<3457@cps3xx.UUCP>
<3528@lindy.Stanford.EDU>
<3537@ursa-major.SPDCC.COM>
<3538@ursa-major.SPDCC.COM>
<3539@ursa-major.SPDCC.COM>
<3606@ddsw1.MCS.COM>
<398@bpdsun1.UUCP>
<4100@tekig4.LEN.TEK.COM>
<41591@bbn.COM>
<41594@bbn.COM>
<418@tahoma.UUCP>
<4217@oregon.uoregon.edu>
<425@edai.ed.ac.uk>
<426@edai.ed.ac.uk>
<426@edai.ed.ac.uk>
<427@edai.ed.ac.uk>
<4322.249A6CBB@stjhmc.fidonet.org>
<4323.249A6CBF@stjhmc.fidonet.org>
<4324.249A6CC2@stjhmc.fidonet.org>
<43535@codas.att.com>
<4409@crash.cts.com>
<4409@crash.cts.com>
<45000030@uxe.cso.uiuc.edu>
<469@extro.ucc.su.oz>
<469@extro.ucc.su.oz>
<4723@sybase.sybase.com>
<4725@sybase.sybase.com>
<474@sdcc15.ucsd.edu>
<4852@teklds.CAE.TEK.COM>
<487@westc.UUCP>
<489@westc.UUCP>
<507@limbic.UUCP>
<516@vice2utc.chalmers.se>
<547@daitc.daitc.mil>
<5534@rpi.edu>
<5570217@hpfcdc.HP.COM>
<5570218@hpfcdc.HP.COM>
<5570219@hpfcdc.HP.COM>
<56225@linus.UUCP>
<60@wells.UUCP>
<610774.890618.KFL@AI.AI.MIT.EDU>
<6198@pdn.paradyne.com>
<6198@pdn.paradyne.com>
<6198@pdn.paradyne.com>
<632@ispi.UUCP>
<653@lopez.UUCP>
<655@biar.UUCP>
<659@whizz.uucp>
<670053@hpcilzb.HP.COM>
<678@ihf1.UUCP>
<680@argon.UUCP>
<68@enea.se>
<693@uvicctr.UVic.ca.UUCP>
<703@oliver.cvedc.prime.com>
<7199@c3pe.UUCP>
<7209@ecsvax.UUCP>
<733@xroads.UUCP>
<744@Terra.cc.brunel.ac.uk>
<7559@cbnews.ATT.COM>
<7560@cbnews.ATT.COM>
<779@redsox.bsw.com>
<780@redsox.bsw.com>
<780@redsox.bsw.com>
<7817@bsu-cs.bsu.edu>
<7818@bsu-cs.bsu.edu>
<781@redsox.bsw.com>
<783@redsox.bsw.com>
<783@redsox.bsw.com>
<783@redsox.bsw.com>
<797@acorn.co.uk>
<7@intiar.EDU.ar>
<7@intiar.EDU.ar>
<7@intiar.EDU.ar>
<81452@ti-csl.csc.ti.com>
<8389@killer.DALLAS.TX.US>
<8389@killer.DALLAS.TX.US>
<8400@killer.DALLAS.TX.US>
<859@hcx1.UUCP>
<8709@chinet.chi.il.us>
<8717@chinet.chi.il.us>
<8719@chinet.chi.il.us>
<8722@pucc.Princeton.EDU>
<8776@xenna.Encore.COM>
<8906180042.AA10334@cunixd.cc.columbia.edu>
<8906181801.AA03935@beta.lanl.gov>
<8906190225.AA10350@helios.tn.cornell.edu>
<8906190231.AA10422@helios.tn.cornell.edu>
<895@gould.doc.ic.ac.uk>
<913@prlhp1.prl.philips.co.uk>
<9484@boulder.Colorado.EDU>
<94@coms.fr>
<9700016@m.cs.uiuc.edu>
<Added.wYak_n200Ui3MI4E86@andrew.cmu.edu>
<BOB.89Jun17141354@giza.cis.ohio-state.edu>
<Jun.18.00.34.37.1989.27194@topaz.rutgers.edu>
<Jun.18.22.00.00.1989.2673@athos.rutgers.edu>
<Jun.18.22.09.08.1989.2725@athos.rutgers.edu>
<Jun.18.22.12.24.1989.2747@athos.rutgers.edu>
<Jun.18.22.53.24.1989.2911@athos.rutgers.edu>
<SHIRONO.89Jun17190318@hcx3.ssd.harris.com>
<SHIRONO.89Jun17190318@hcx3.ssd.harris.com>
<ZMACV91.89Jun16093228@flamingo.doc.ic.ac.uk>
<telecom-v09i0202m01@vector.dallas.tx.us>
<telecom-v09i0202m02@vector.dallas.tx.us>
<telecom-v09i0202m03@vector.dallas.tx.us>
<telecom-v09i0202m04@vector.dallas.tx.us>
<telecom-v09i0202m05@vector.dallas.tx.us>
<telecom-v09i0202m06@vector.dallas.tx.us>
<telecom-v09i0202m07@vector.dallas.tx.us>
<telecom-v09i0202m08@vector.dallas.tx.us>
<telecom-v09i0202m09@vector.dallas.tx.us>
-------------------------- cut here -----------------------------
:: Jeff Makey
Department of Tautological Pleonasms and Superfluous Redundancies Department
Disclaimer: Logicon doesn't even know we're running news.
Internet: Makey@LOGICON.ARPA UUCP: {nosc,ucsd}!logicon.arpa!Makeyclewis@eci386.UUCP (08/04/89)
In article <651@vector.Dallas.TX.US> chip@vector.Dallas.TX.US (Chip Rosenthal) writes: |In article <43675@bbn.COM> denbeste@BBN.COM (Steven Den Beste) writes: |I went through the entire comp.all heirarchy here looking for messages |with "!sunybcs!" in the Path dated July 22nd. I came up with *325* |messages. Attached below is a shar archive with: (1) the message-id's |from these 325 articles, and (2) a script to read message-id's from the |standard input and cancel them locally. |If you want to zap these messages, run: | sh do-cancel < bogus-mssgid WARNING: if you have C-news, extreme caution is advised... At least in some versions, inews forks itself off into the background and runs lots of processes and is slow. Next thing you know, performance down the tubes, and blown process table. If someone has a version of do-cancel that works via stuffing batches into rnews, it would be much appreciated. For the moment, I've created a version of inews that doesn't fork, though I expect it to take several hours to run the several hundred cancels. -- Chris Lewis, R.H. Lathwell & Associates: Elegant Communications Inc. UUCP: {uunet!mnetor, utcsri!utzoo}!lsuc!eci386!clewis Phone: (416)-595-5425
chip@vector.Dallas.TX.US (Chip Rosenthal) (08/04/89)
clewis@eci386.UUCP (Chris Lewis) writes: >[re: problems with running do-cancel under C-news] >For the moment, I've created a version of inews that doesn't fork, >though I expect it to take several hours to run the several hundred >cancels. Yoicks. Is that really true? It took me about 5 mins to run the thing here under B2.11 on a 386. BTW, in answer to those who are wondering why these messages weren't rejected by history, the offending site stepped on the "Date:" header. I've been told that TELECOM Digest issue 202 was reposted to comp.dcom.telecom in this slew of messages. Well, I sent out that issue on June 18. -- Chip Rosenthal / chip@vector.Dallas.TX.US / Dallas Semiconductor / 214-450-5337 "I wish you'd put that starvation box down and go to bed" - Albert Collins' Mom
henry@utzoo.uucp (Henry Spencer) (08/04/89)
In article <653@vector.Dallas.TX.US> chip@vector.Dallas.TX.US (Chip Rosenthal) writes: >>For the moment, I've created a version of inews that doesn't fork, >>though I expect it to take several hours to run the several hundred >>cancels. > >Yoicks. Is that really true? It took me about 5 mins to run the thing >here under B2.11 on a 386. Might be true. C inews is optimized for human posting, not mechanical posting. (Incidentally, the -W option does what Chris wants without software modifications.) Mechanical posting should go through relaynews, which is, uh, fast. -- 1961-1969: 8 years of Apollo. | Henry Spencer at U of Toronto Zoology 1969-1989: 20 years of nothing.| uunet!attcan!utzoo!henry henry@zoo.toronto.edu
rmtodd@servalan.uucp (Richard Todd) (08/08/89)
In article <653@vector.Dallas.TX.US> chip@vector.Dallas.TX.US (Chip Rosenthal) writes: >>For the moment, I've created a version of inews that doesn't fork, >>though I expect it to take several hours to run the several hundred >>cancels. >Yoicks. Is that really true? It took me about 5 mins to run the thing >here under B2.11 on a 386. Well, under C News here on servalan (my Mac IIx, 16MHz 68030 with the stock 28ms Quantum drive, running SVR2), it took an hour and a half. (Granted I had 3 windows up on the console with tails on the various logfiles going, but still...) Face it, C News inews really stinks as far as performance goes. It's written as a shell script. The reasoning behind this is that 1.you want it to be a shell script and 2. unless you spend all your time posting, the vast majority of all articles processed on your machine come in from outside and go straight to relaynews, which is fairly fast. I don't have any good benchmarks on C News vs B News processing of incoming batches, but it seems to take roughly the same amount of time to unpack comparably sized batches of news on servalan and on uokmax (a Multimax running B2.11 News under BSD4.2). Make of that what you will... Anyway, it appears that Spencer and Collyer weren't really desinging the system believing that someone was likely to inject 300 local cancel messages at once. Oh, and according to the C News docs, the -W flag to inews will cause it to not do the fork of relaynews into the background. (I didn't notice this myself until after I had done the mass cancelling; I'd just put a suitably-long sleep in the do-cancel loop). Amazing what you can learn just by reading the documentation :-).
clewis@eci386.uucp (Chris Lewis) (08/08/89)
In article <653@vector.Dallas.TX.US> chip@vector.Dallas.TX.US (Chip Rosenthal) writes: >clewis@eci386.UUCP (Chris Lewis) writes: >>[re: problems with running do-cancel under C-news] >>For the moment, I've created a version of inews that doesn't fork, >>though I expect it to take several hours to run the several hundred >>cancels. > >Yoicks. Is that really true? It took me about 5 mins to run the thing >here under B2.11 on a 386. Quite true - running do-cancel with C news inews modified to not spawn in the background took approximately 3 hours, and (very approx) about 6,000 processes for 600 some-odd articles .... (the 6,000 is very approximate - other activity was going on at the same time and $$ went up by about 12,000 during that time). (16Mhz 386, 386/ix 1.0.6, pre-comp.sources.unix C news.) [In contrast, with an unmodified inews, the system hung up almost completely in 30-40 seconds with lots of simultaneous inews invocations.... Fortunately, I was able to kill it ...] As Henry points out though, this is hardly unexpected. Inews is intended for human-generated messages. If you pump these articles into relaynews directly, I expect it'll only take a few minutes. David Kuder (david@indetech) sent me a modified version of do-cancel that does just this, but I didn't need to run it because I had already run it with a modified inews. I would have posted it, but I haven't asked David for permission. David, if you're reading this, I suggest that you post it. Officially via comp.sources.unix or ...misc would be nice. Or, even integrated with C news or somthin. [Incidentally, we're running a version of C news predating the comp.sources.unix distribution and it doesn't appear to support the -W flag that Henry mentions. One of these days we'll upgrade] On a 3b1, with B2.11 (patch level 14) it took approximately 10 minutes. >BTW, in answer to those who are wondering why these messages weren't >rejected by history, the offending site stepped on the "Date:" header. >I've been told that TELECOM Digest issue 202 was reposted to comp.dcom.telecom >in this slew of messages. Well, I sent out that issue on June 18. I don't think so. History don't know nothing 'bout dates. On our site, the path that these articles took was sufficiently wierd to suggest that some machine held on to them so long that when kicked back out into their outgoing feed, that many sites had expired the message-ids. Then, these articles wandered hither-and-yon seeking sites that had also expired them. However, B-news, I believe, has a facility for rejecting articles that are over a certain age, but the default's rather high (3 weeks if I remember correctly). As a suggestion, people might consider turning this down to a week or so - anything that takes that long to get to you is likely to be a system vomiting its spool rather than true slow delivery. -- Chris Lewis, R.H. Lathwell & Associates: Elegant Communications Inc. UUCP: {uunet!mnetor, utcsri!utzoo}!lsuc!eci386!clewis Phone: (416)-595-5425
greenber@utoday.UUCP (Ross M. Greenberg) (08/09/89)
In article <1989Aug7.230146.274@servalan.uucp> rmtodd@servalan.UUCP (Richard Todd) writes: > Face it, C News inews really stinks as far as performance goes. It's written >as a shell script. The alternative might be run C News inews through a shell compiler, such as Comeau Computing's CCsh. Turns it into a C program rather nicely. -- Ross M. Greenberg UNIX TODAY! 594 Third Avenue New York New York 10016 Review Editor Voice:(212)-889-6431 BBS:(212)-889-6438 uunet!utoday!greenber BIX: greenber MCI: greenber CIS: 72461,3212
yost@esquire.UUCP (David A. Yost) (08/15/89)
In article <43675@bbn.COM> denbeste@BBN.COM (Steven Den Beste) writes: >Today we received a large number of news articles dated July 22, which we have >received before. I located 50 or so of them and analyzed the paths by which >they arrived here. Today alone, we have 1,883 duplicate messages in comp alone. We may have some other problem. Enclosed is a shell script that will find duplicate messages and list their pathnames. Its implementation required another interesting, more generally useful utility which I've wished I had for a long time and finally wrote. Here is quickie documentation on both scripts, followed by a shar of the two scripts. --dave yost ----------------- Usage: find newsdir ... -type f -print | newsdups [ -i file ] [ -o file ] Takes news file pathnames on standard input and outputs pathnames of later-numbered duplicate messages in each group. If the -o file argument is used, newsdups also outputs a record of the message IDs seen in this pass into the specified file for use as the -i file argument to a future run of newsdups, at which time newsdups will assume that those message IDs already exist. ----------------- Usage: numdups awk-field-number-list file ... For each line, prints a number n followed by a space followed by the original text on the line. The number identifies the line as the nth line containing the specified fields. If multiple field numbers are specified, they must be separated by spaces, and the awk-field-number-list argument must be quoted. Fields are numbered as in awk (0 = whole line, 1 = field 1, 2 = field 2, etc.). ----------------- #!/bin/sh unlink=NO case $1 in -u) unlink=YES shift esac echo x newsdups case $unlink in YES) rm -f newsdups esac sed 's/^X//' >newsdups <<'*-*-END-of-newsdups-*-*' X#!/bin/sh X X# See "Usage:" below X# X# Requires the nonstandard shell script 'numdups' X# X# 890814 D Yost, Davis Polk & Wardwell X# X# Why the tmp1 file instead of a pipe? Otherwise it doesn't work. X Xcase $# in X0 | 2) ;; X*) echo 1>&2 " XUsage: find newsdir ... -type f -print | newsdups [ -i file ] [ -o file ] X XTakes news file pathnames on standard input and outputs Xpathnames of later-numbered duplicate messages in each group. X XIf the -o file argument is used, newsdups also outputs a record of Xthe message IDs seen in this pass into the specified file for use Xas the -i file argument to a future run of newsdups, at which time Xnewsdups will assume that those message IDs already exist. X" X exit 2 Xesac X Xtmp1=/tmp/newsdups1.$$ Xtmp2=/tmp/newsdups2.$$ Xtmp3=/tmp/newsdups3.$$ Xtrap "status=$? ; rm -f $tmp1 $tmp2 $tmp3 ; exit $status " \ X 0 1 2 3 4 5 6 7 8 10 12 13 15 24 25 29 X Xifile= Xofile=$tmp2 X Xcase "$1" in X-i) ifile=$2 ; shift ; shift ;; X-o) ofile=$2 ; shift ; shift ;; Xesac X Xxargs grep -i '^message-id:' > $tmp1 Xsed < $tmp1 's,/\([^/:]*\):[^:]*: , \1 ,' \ X| awk '{printf "%s %07d %s\n", $1, $2, $3}' \ X| sort > $ofile X Xcase "$ifile" in X"") cat $ofile X ;; X*) numdups '1 3' $ifile \ X | awk '$1 == 1 { print $2, $3, $4 }' > $tmp3 X cat $tmp3 $ofile X ;; Xesac \ X| numdups '1 3' \ X| awk '$1 != 1 { printf "%s/%d\n", $2, $3 }' X Xexit *-*-END-of-newsdups-*-* echo x numdups case $unlink in YES) rm -f numdups esac sed 's/^X//' >numdups <<'*-*-END-of-numdups-*-*' X#!/bin/sh X Xcase $# in X0) echo 1>&2 " XUsage: numdups awk-field-number-list file ... X XFor each line, prints a number n followed by a space followed Xby the original text on the line. The number identifies the Xline as the nth line containing the specified fields. XIf multiple field numbers are specified, they must be separated Xby spaces, and the awk-field-number-list argument must be quoted. XFields are numbered as in awk (0 = whole line, 1 = field 1, X2 = field 2, etc.). X" X exit 2 Xesac X Xfield=$1 ; shift X Xtmp=/tmp/numdups.$$ Xtrap "status=$? ; rm -f $tmp ; exit $status " \ X 0 1 2 3 4 5 6 7 8 10 12 13 15 24 25 29 X X( Xecho -n "awk '{ X tmpstr = sprintf "'"' X Xfor X in $field Xdo X echo -n "%s " Xdone X Xecho -n '"' X Xfor X in $field Xdo X echo -n ', $'"$X" Xdone X Xecho ' X ++counts[tmpstr] X printf "%d %s\n", counts[tmpstr], $0 X}'"' $*" ) > $tmp Xsh $tmp *-*-END-of-numdups-*-* exit