[nos-bbs] DUPES and staggered forwarding
Michael Fox - N6MEF
n6mef at mefox.org
Wed Oct 21 11:32:21 EDT 2020
We schedule our forwarding using "at". While long sessions can overlap,
perhaps the staggering has prevented the problem for us.
If I remember correctly, one thing that was annoying about that was the
inability to schedule two forwarding session at the same minute. I think I
got back some type of "busy" message. (At work, can't test right now.)
Since forwarding can occur with more than one BBS at a time, it would be
nice if this limitation didn't exist for scheduled forwarding.
From: nos-bbs <nos-bbs-bounces at lists.tapr.org> On Behalf Of Langelaar
Sent: Wednesday, October 21, 2020 7:55 AM
To: TAPR xNOS Mailing List <nos-bbs at lists.tapr.org>
Subject: [nos-bbs] DUPES and staggered forwarding
If I did not know any better, and this is a very recent observation,
and perhaps a FLAW ? if you have multiple systems (even 2) connecting
to you, and each is sending a proposal for the same message, same bid,
and IF they are within seconds of each other, seems they are ALL (both)
Processing the one does not give enough time to update history file, and
both are accepted when the proposals come in. I will need to fix that !
So may I suggest staggered instead of 'aggressive, all remote forwarding
partners at the same time' as an interim fix, or am I getting it wrong ?
First time I've seen this directly, and that was my first take on it. I
personally have never seen this situation on my JNOS setup, never ! But
I also have minimal number of forwarding partners and they all do their
thing like 15 minutes apart type of arrangement. Even if it's a fluke,
most likely it has happened, just didn't notice.
There is NO way these two sample messages I just saw this morning should
have been accepted, one was direct from me, the other from GB7CIP, both
looked absolutely fine to me.
nos-bbs mailing list
nos-bbs at lists.tapr.org
More information about the nos-bbs