Subj : Re: %HELP ?
To : Nick Andre
From : Wilfred van Velzen
Date : Wed Jan 18 2017 07:30 pm
Hi,
On 2017-01-18 12:45:23, Nick Andre wrote to Wilfred Van Velzen:
about: "Re: %HELP ?":
WV>> NA> -R to RESCAN connected areas.
WV>>
WV>> Isn't that a very dangerous option? It's only save for nodes with no
WV>> other links, otherwise a massive dupe dump would be generated.
NA> Wrong, and not any more dangerous than any other tosser that has Rescan.
NA> A tosser has an area called ABC. There are three downlinks. 229/100,
NA> 229/200 and 229/300. A new system, 229/400 joins and Areafixes ABC with a
NA> rescan. They get all the messages but 100, 200 and 300 do not because they
NA> exist in the Seen-by's in all the messages that exist already, and thus
NA> 229/400 is added into the Seen-by's/Path going forward.
In that case there won't be too much danger. But your thinking too much about
the fidonet structure of the 80's and 90's. The new node that does the
rescanning today, is likely to have a few other links outside the net and/or
zone, that won't be in the seenby's.
NA> The method used is no different than Gecho, TBBS/Flame and a lot of
NA> tossers out there... pretty sure even Fastecho does it this way but
NA> perhaps adds some extra kludging to indicate that the message was in
NA> fact, rescanned.
The danger of the d'Bridge rescan is that it does a full rescan of all
connected area's. Most tossers have commands to just rescan newly added areas,
or just rescan a single area, and limit the number or date range of messages.
For instance fastecho has the following commands regarding rescanning:
%RESCAN <- Rescan following area(s) and add if area(s)
FASTECHO.GER is/are not linked yet
%DAYS 7 <- Rescan only messages not older than 7 days
SHAREWRE
%MSGS 100 <- Rescan at most 100 messages each area
FE_HELP
FDECHO, R <- Alternative way to rescan a single area
FDECHO.GER, R=300 <- Rescan up to 300 messages of that area
