On 18 Sep 2019 at 08:17p, Jeff Smith pondered and said...
 
 JS> Hello There,

Hi :)

 JS> I am contining to have a problem with stale or undeleted busy files. I

Hmm

 JS> have decided to use the unprefered option of setting up an event to
 JS> periodically use FIDOPOLL to kill all busy files. As it looks like
 JS> FIDOPOLL doesn't always delete the busy file. Looking at the logs seems
 JS> to indicate the the FIDOPOLL connection doesn't always end completely or
 JS> correctly while at other times in the log the connection does complete
 JS> with the same remote system. Curreently "My" Mystic only connects to two
 JS> remote systems. A BBBS system and a BinkD system. My presumption is that
 JS> either BinkD isn't completing the connection ORFIDOPOLL isn't detecting
 JS> the connection being completed and then doesn't remove the busy file.

Using fidopoll killbusy all is the best way to remove stale BSY files. Mystic
creates BSY files to ensure another process is not running while node
activity is happening when packets are being moved about, processed etc.

If you are having issues intermittently I'd try and pin down if it is post a
fidopoll session with a given node / system connecting to. I can say here I
poll internally a BinkD system without issue.

 JS> This last busy period lasted the better part of 24 hours. I have since
 JS> added a Mystic event to delete all busy files once every 12 hours until
 JS> a better solution to the busy is sue can be found.  
 
BSY files that remain are symptomatic of a wider issue. I could even be
corrupt echomail node data within your Mystic, I've seen that in the past but
if the problems seem to be related to a failed fidopoll then yep that could
easily cause an issue if the exe locks up..

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)