ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÚ¿ÚÄ¿ÚĿڿ Your test was received here on 2022-03-09 01:54:47 and it looks
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
If this is true, 3hrs 46min, then I prolly don't have my crash running, huh?
Or, I guess maybe its set to send when the user logs off - I stay
idling, often for hours...
Are my two thoughts above correct? I am thinking its the latter, which
is fine, but maybe I need to check crash... [on all my FTNs]
Ú¿ÚÄ¿ÚĿڿ Your test was received here on 2022-03-09 01:54:47 and itlooks
³ ³ÄÙÀÄ¿ ³ like you sent it on 2022-03-08 22:08:40. If that is correct,
Á ÀÄÙÀÄÙ Á then it took 3 hours 46 minutes 7 seconds to get here.
If this is true, 3hrs 46min, then I prolly don't have my crash running, huh?often for hours...
Or, I guess maybe its set to send when the user logs off - I stay idling,
Are my two thoughts above correct? I am thinking its the latter, which isfine, but maybe I need to check crash... [on all my FTNs]
I will speak to Deon about it, just in case it's something network related. We can do a test locally too, so you send a message and I see when I get it on my bbs, but as I say above, I think you're ok and its just a delay between hub3 and hub2.
It could be one of three things:[BBS Clock, Timezone or Delay]
I dont recall if in the ping reply, I include the Via lines - which
should also help figure out where the delay might be.
In fact, if you have the msgid (dont recall if I include that in the
reply - I should), then you can find the message on the clrghouz with it.
Sysop: | CyberNix |
---|---|
Location: | London, UK |
Users: | 20 |
Nodes: | 10 (0 / 10) |
Uptime: | 99:06:48 |
Calls: | 880 |
Files: | 4,190 |
Messages: | 637,829 |