mark@umcp-cs.UUCP (10/03/83)
This has been happening to us as well. It just started about 3 weeks
ago, the double messaging with LONG delays. I haven't tracked
down the paths of the duplicates yet, but I will if someone
thinks there is anything that can be done about it.
--
spoken: mark weiser
UUCP: {seismo,allegra,brl-bmd}!umcp-cs!mark
CSNet: mark@umcp-cs
ARPA: mark.umcp-cs@UDel-Relaysdo@u1100a.UUCP (10/04/83)
I think I can shed some light on the reappearance of articles weeks
after they first appear. As we all know, articles get dropped
now and then. Some connections are worse than others. We have
a set of shell procedures which allow a history file to be compared
against a master history file, and the missing news items transferred
and posted on the system with the missing articles.
I believe this was done using our history file as the master.
The other site doesn't have a news link with us.
The other site then posted all the transferred articles. Since
we are not in its sys file, the articles were re-sent out over
the standard news links. Any articles near their expiration
date probably expired by the time far away machines received them.
All this probably only accounts for a few duplicates. I'm sure
there are many other ways for dups to appear, including the
famous runaway notesfiles occurrences. If you don't see abnjh!u1100a
in the news path, then it's not this problem.
Scott Orshan
Bell Labs Piscataway
201-981-3064
{pyuxi,houxm,ihnp4}!u1100a!sdoadrian@ru-cs44.UUCP (Adrian Pell) (10/14/83)
Do you often get that feeling that "I've seen this before"?? Well, it's been happening to me a lot recently, and some investigation revealed that a number of net articles have been arriving here in the UK twice, the second more that a fortnight after the first. Consider the following diff: ============================= line 3 in '<', /usr/spool/oldnews/net/news/267 changed from line 3 in '>', /usr/spool/news/net/news/359: < Path: ru-cs44!ukc!vax135!ariel!hou5f!hou5g!hou5h!eagle!mhuxt!mhuxi!cbosgd!ihnp4!we13!burl!spanky!ka --- > Path: ru-cs44!ukc!vax135!floyd!whuxlb!pyuxll!abnjh!u1100a!pyuxn!pyuxi!mhuxm!mhuxd!mhuxa!ulysses!cbosgd!ihnp4!we13!burl!spanky!ka line 11 in '<', /usr/spool/oldnews/net/news/267 changed from line 11 in '>', /usr/spool/news/net/news/359: < Date-Received: Thu, 8-Sep-83 19:19:18 BST --- > Date-Received: Thu, 29-Sep-83 18:46:17 BST ============================= This article (spanky.475) was originally posted on Sep. 7 and made it all the way to the UK in about a day by the short route. However, something along the long route delayed it by another 3 weeks, by which time to original article has disappeared from history. I hesitate to suggest that the default expiry time should be longer since news space is not totally limitless, but .... Wouldn't it be better to try and iron out some of the news loops around the US, which should, I suppose, reduce the amount of net traffic. Any thoughts? -- Adrian Pell ({vax135,mcvax,edcaad}!ukc!ru-cs44!adrian) Computer Science Dept. University of Reading UK