I've been having issues with the semaphores and Events in general. I believe the issues are self caused due to not really understanding the Events setup
in mystic. The first thing I noticed was mailin was failing and found when I did a restart it worked fine. Generally I found in time the whole Event setup seemed to stop working. I also noticed mailin was Event 10 or so and mailout was Event 5. So Events appear to run from 1 to whatever is last. I have now moved all my semaphore events to the top of the list and put loglevel-3 so
I see more of what's going on.
So, if you are having issues with semaphores in mystic, try moving those
Events to the top (1-5 or so). My reasoning is semaphore run Events are the most likely to work and less likely to hang things. Also put loglevel up to
3 or fully debug level so you can see what's going on in the logs. Being Linux I put rare Events that stop working in cron with full paths and will be working to get then all back to Events when I figure out what I've done to hang them ;)

--- Mystic BBS v1.12 A47 2021/04/08 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)

On 11 Apr 2021, bcw142 said the following...

I've been having issues with the semaphores and Events in general. I believe the issues are self caused due to not really understanding the Events setup in mystic. The first thing I noticed was mailin was failing

perhaps as an exercise .. do you have "Page Sysop" configured on any of your menus?

you could change it to do something like:

GP - Page Sysop For Chat
!C - Create Semaphore File

and attempt to make the events system send you emails after a user tries to page you.

or perhaps create a sysop command for the message menu that creates the semaphore for triggering (so in this case "forcing") a message poll.

--- Mystic BBS v1.12 A47 2021/04/08 (Windows/32)
* Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)