TID: Mystic BBS 1.12 A48
MSGID: 1:129/215 7c771c0f
REPLY: 1:267/157 23aa4e57
TZUTC: -0500
 AD> well. The semaphore issue also was happening quite a bit when I had my
 AD> call out time scheduled for the top of the hour at the same time most of
 AD> my hubs were calling into me. At first I took to just running an event

Thank you for the feedback, it is much appreciated.

I think what I need to do is to set up my BBS again so that its running with
networks crashing messages to me.  I hope that way I'll see it happening and I
can get this resolved.

You are right that deleting the semaphores automatically can cause some
problems too in cases where they should be there.  Its kind of a grey area
though considering they are also getting stuck for you.

... Intelligence tests are biased toward the literate.

--- Mystic BBS v1.12 A48 2022/12/30 (Windows/64)
 * Origin: Sector 7 * Mystic WHQ (1:129/215)
SEEN-BY: 1/123 15/0 90/1 105/81 106/201 114/705 120/340 616 123/10
SEEN-BY: 123/120 131 129/215 305 153/7715 154/10 30 40 50 700 218/840
SEEN-BY: 220/70 90 221/6 226/17 18 30 70 100 227/114 201 229/110 111
SEEN-BY: 229/112 113 114 206 275 307 310 317 400 424 426 428 452 470
SEEN-BY: 229/550 664 700 250/5 8 266/512 267/800 280/464 282/1038
SEEN-BY: 292/854 298/25 301/1 305/2 3 317/3 320/219 322/757 342/200
SEEN-BY: 396/45 460/58 633/280 712/848 770/1 2320/105 3634/12
PATH: 129/215 154/10 770/1 317/3 229/426