Greetings Human -
It is I... Todd FSXnet hub 2

Welp I have been getting intermittent .BSY lock ups at FSXnet hub 2
Usually I catch these but sometimes I don't and and it puts a stop to all the mail . I think its due to file toss ... so with that being said here are my thoughts ..

1: Some sort of monitoring done by mystic to check for .BSY lockups , have mystic identify the lock up , purge the .BSY files , and restart mystic

2: A command line switch so I shut down mystic CLEAN, then I can write a batch file to do a once or twice a day shutdown and restart with .BSY purge .

AnyWHo any help would be great . By the way In running Windows 10 64 Bit.
Im not sure why but im going show you my "Mystic Keep Alive" script below. which recovers mystic of the program it self crashes .

@ECHO ON
Z:
cd\mystic\semaphore\
del *.BSY
cd\mystic
FIDOPOLL KILLBUSY
:LOOP
MIS -SERVER
TIMEOUT /T 5
GOTO LOOP

|08Sys|05op So|13laRis
|13 Err|05or 12|0802 and |10Er|02ror |104|080|024 B|08BS !
|15FSXnet HuB 2 T|07holian A|08DmiN !


--- Mystic BBS v1.12 A45 2020/02/18 (Windows/64)
* Origin: Error 1202 BBS (21:2/1202)

have mystic identify the lock up , purge the .BSY files , and restart mystic

Mystic already does this after 2 hours.

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/64)
* Origin: Sector 7 (21:1/108)

Mystic already does this after 2 hours.

Error 404 and FSXnet hub 2 both suffer from intermittent .BSY lockups . can
you point me into a direction to start trouble shooting ..
Could me backing up mystic with a batch file cause a .BSY lockup if tossing while the batch back up program is running ?
Thanks

|08Sys|05op So|13laRis
|13 Err|05or 12|0802 and |10Er|02ror |104|080|024 B|08BS !
|15FSXnet HuB 2 T|07holian A|08DmiN !


--- Mystic BBS v1.12 A45 2020/02/18 (Windows/64)
* Origin: Error 1202 BBS (21:2/1202)

Error 404 and FSXnet hub 2 both suffer from intermittent .BSY lockups . can you point me into a direction to start trouble shooting ..
Could me backing up mystic with a batch file cause a .BSY lockup if tossing while the batch back up program is running ?

Well the BSY scale thing after 2 hours wasn't working in A45 so that is one issue, obviously not the cause but the reason Mystic isn't "fixing itself". So having that fixed alone should make a huge difference.

Backing things up should be okay I think, but if you back up while something is running and then restore the backup, that would absolutely create a BSY issue if you did it while things were running. As part of restoring a backup you should probably run "fidopoll killbusy all" while everything is offline just to make sure its clear.

Lots of things can cause the BSY files to become stale. If you have a running process and it gets interrupted for any reason (a crash, user forces it shut,, shutting down the OS, etc) it can leave unaddressed BSY files.

Also people running killbusy in batch files cause it themselves by creating situations where MUTIL and FIDOPOLL are running concurrently when they shouldn't. Bugs, crashes, user error all sorts of reasons. Even when something like a crash happens Mystic should fix itself by clearing BSY and ghost nodes and at least in the case of BSY that wasn't happening in A45 and who knows for how long before that.

--- Mystic BBS v1.12 A46 2020/02/26 (Windows/64)
* Origin: Sector 7 (21:1/108)