Subj : Re: InterBBS Last Callers
To   : xqtr
From : Codefenix
Date : Wed Jul 16 2025 08:03 pm

  Re: Re: InterBBS Last Callers
  By: xqtr to slacker on Tue Jul 15 2025 03:45 pm

 xq> Another solution, would be to create a log, but i don't think that many
 xq> people would look into that. :)

You underestimate sysops. Plenty know to check logs for errors, and do.

 xq> It's preferred to check the FSX_DAT or any other echonet area that handles
 xq> the data packets (for FSX, is FSX_DAT) for corrupted messages or a wrong
 xq> set up BBSes and report to the BBS sysop or a FSX admin.

No disrespect, but no. It's not fsxNet's fault that the script is failing to process a message. The script should be more fault-tolerant of unexpected scenarios like the one described here, and handle it gracefully.

 xq> To bypass the problem, just delete the FSX_DAT.* files, which will erase
 xq> all messages, along with the corrupted ones ;) The echonet, will be
 xq> re-created when it receives new messages.

This gets around the current problem at hand, sure. But only until it re-surfaces. Then the sysop (in fact, all sysops who use this script) will inevitably find themselves in the same situation again.

The script needs to be fault-tolerant.

|15 þ ù ú codefenix ú ù ú ConstructiveChaos BBS ú ú ù þ þ
|08 þ þ ù (https/telnet/ssh)://conchaos.synchro.net ú ù þ
|07
--- SBBSecho 3.28-Win32
 * Origin: -=[conchaos.synchro.net | ConstructiveChaos BBS]=- (21:4/141)

.