sjg@melb.bull.oz.au (Simon J Gerraty) (01/17/91)
This problem has started only recently. I noticed that the amount of news being shipped to one of my feedees (zen) had increased dramatically. I had recently changed the sys entry (changed comp.sources.unix to comp.sources). I have noticed that articles from NEWSARTS/junk were being sent to zen. Here is zen's entry in NEWSCTL/sys I have only broken it into multiple lines (incase it broke something as it was). # # ACSnet feeds # zen:!all,!all.all,control,news,gnu,aus.sources,aus.archives,aus.acsnet,\ aus.netstatus,aus.aarnet,aus.auug,aus.general,aus.jobs,aus.sun-works,all.tex,\ comp.emacs,comp.sources,alt.sources,all.sun,comp.lang.c,comp.lang.c++,\ comp.unix,!all.aix,!all.aux,!all.ultrix,!bull,!bull.all/world,mel,vic,aus:f: It is quite long (it is supposed to be a limited feed :-) Is it too long perhaps? The !all,!all.all was an attempt to remove junk/* from the feed. Here is the tail of the current NEWSARTS/out.going/zen/togo ** /usr/spool/news/comp/unix/aix/1267 1048 /usr/spool/news/alt/sources/wanted/186 1361 /usr/spool/news/comp/unix/sysv386/3186 1627 /usr/spool/news/comp/unix/shell/959 1352 /usr/spool/news/comp/unix/programmer/697 1950 /usr/spool/news/comp/unix/wizards/449 1719 /usr/spool/news/comp/lang/c/3477 1018 /usr/spool/news/comp/unix/sysv386/3188 1535 ** /usr/spool/news/comp/unix/aux/994 1027 ** /usr/spool/news/unix-pc/general/498 1035 /usr/spool/news/comp/unix/sysv386/3189 1891 /usr/spool/news/comp/lang/misc/953 13869 ** /usr/spool/news/junk/9472 1187 /usr/spool/news/comp/sources/bugs/224 36726 The lines I have flaged with ** should _not_ be there. Yes the tail of togo was written after the sys file. I am running C News patched to 7-Sep-90 on a Bull DPX/2-340 running System V R3 -- Simon J. Gerraty <sjg@melb.bull.oz.au> #include <disclaimer,_witty_comment>
henry@zoo.toronto.edu (Henry Spencer) (01/18/91)
In article <1991Jan16.234551.22017@melb.bull.oz.au> sjg@melb.bull.oz.au (Simon J Gerraty) writes: >** /usr/spool/news/comp/unix/aix/1267 1048 >** /usr/spool/news/comp/unix/aux/994 1027 >** /usr/spool/news/unix-pc/general/498 1035 >** /usr/spool/news/junk/9472 1187 > >The lines I have flaged with ** should _not_ be there. You need to investigate the articles much more carefully before saying that, for several reasons: 1. A cross-posted article will go in the batch file by the name of its first group, but will be sent if *any* of the groups should be sent, so the name in the batch file doesn't mean much. 2. There is nothing abnormal about a "junk" article being retransmitted. Transmission is determined by the groups given in the article, not by where it got filed. If an article shows up in comp.frobozz, and you don't have that group, the article will be filed in junk... but if your sys file says to pass comp.frobozz on to your neighbors, the article will be passed on. I would urge you to read the news(5) and relaynews(8) manual pages very carefully. The policy issues here are complex and subtle, and it took a lot of thought to get them right. 3. The comp.unix.* articles are quite legitimate; your sys-file line says to send them. "!all.aix" excludes "foo.aix" but not "comp.unix.aix". Again, I think a reading of news(5) is in order -- it defines the newsgroup name-matching algorithm precisely. -- If the Space Shuttle was the answer, | Henry Spencer at U of Toronto Zoology what was the question? | henry@zoo.toronto.edu utzoo!henry