On 01/06/17, Rudi Timmermans said the following...
 
 RT> Hi Paul,
 RT> 
 RT>  PH> Use of fidopoll killbusy all   is *not* recommended as part of a batc
 RT>  PH> file etc to try and fix a bigger problem.

I actually run a Windows logoff script when it does its scheduled two week
server restart, and the only thing I've found that's
"kill-friendly" for MIS
is just Windows' taskkill without the /f switch. It works, and until I
started using that recently I just restarted the VM with MIS still running. 

Since it might have had semaphores still extant, I would also run the
killbusy on server restart. taskkill seems a lot more graceful than just
popping MIS out of existence on restart, but I'm always a bit worried that
those semaphores still remain. Hence, I still have killbusy on the startup
script. 

No issues that I've seen, and it's been like that on my server since g00r00
implemented it. Of course, I have it run before MIS is started back up, so
maybe the possible issue was running it while MIS was up? Not sure.

--- Mystic BBS v1.12 A31 (Windows)