Digital Man wrote to mark lewis <=-
Re: SBBSecho logging.
By: mark lewis to Digital Man on Wed Dec 30 2015 06:55 pm
Do you know that raw packets are being sent in this case? That is a pretty uncommon configuration.
no, i don't know how joe, michiel and wilfred are set up...
as for uncommon configuration, i switched to raw PKTs years ago... there's no need for bundles, really, when the mailers can compress better on the fly during transmission... then again, i also switched because some of my downlinks
were in really rough areas and pulling one large bundle was tough but they could pull lots of smaller PKTs over several connections without having to start all over at the beginning again ;)
And you're using SBBSecho in this configuration? It be good to know
that at least one sysop is testing that feature. :-)
Joe Delahaye wrote to Bill McGarrity <=-
Re: Re: SBBSecho logging.
By: Bill McGarrity to Digital Man on Wed Dec 30 2015 23:01:00
Echomail packets are bundled into archives and those bundles are
what is sent to the downlinks. Are you wanting to know the name of
the bundle files created or the actual packets within those bundles?
BinkD has no knowledge of the packets within a bundle it sends or
receives, so I'm not clear how the packet filename (which is what I
assume you meant by "pkt #" in your msg) from the SBBSecho log would
help you. I can add more log output, but if it is too much or the
wrong kind, then that's not going to be helpful to you (or whomever
is having the issue). More clarity is needed.
I don't compress here so binkd sees the pkt #'s that are being sent.. even though there maybe 4 to 5 being sent during one connection to that node.
My request is to log the actual PKT # sbbsecho creates so we can compare the creation, the sending and receiving on one end (anyone who's running sbbsecho for instance). The node in question (non Synch user), says they're not receiving any pkt's being delivered or showing in the bit bucket or being stored in the bad pkt area on his system.
Creating one test message and sending it to the two systems should resolve the issue either way. If there is an issue with sbbsecho (highly doubt), then you'll have some more info to resolve it.
The above is already being tested. We found that although the packet
name at least was created, (archived), when the connections were made,
the mail went to the one system, and tried to send to the other, but
file not found.
Lord Time wrote to Bill McGarrity <=-
OK... that is quite possible. Naturally I run fidoin when I get something from my uplink and then it processes it to downlinks but I also have a timed event fidoout running every 10 minutes for netmail to be processed. There could be an overlap. Interesting...
hmmm, you run fidonin way more then I do, mine is set at every 15 mins
(96 times a day), I figure as a fidonet hub boss, my net (league 10), whispernet hub, (was another net hub) every 15 mins would be enought
|Riverside County, California
|15 (0 / 15)