1. Forum
  2. FSXNet
  3. FSX MYS

  • Re: Having to kill fidopoll

    From g00r00@21:1/108 to PalKat on Wed Feb 26 19:36:18 2020

    Are you using [FileToss] by chance? Someone suggesting they think th is actually a problem with that function.

    Yes, my mailin.ini is using FileToss.

    Thanks. I start with looking into FileToss a bit more as that was the only thing in any sort of recent time that had changes to the BSY file system.

    Is there something I should be looking for in the logs specific to this? if so which log file?

    No not really. The files should be fine on their own and even if they ever
    did get stuck they should unstick themselves after 2 hours, so something is going on here.

    I had a "busylog.txt" active for probably 2 years and in that time no one was reporting much of anything to me for many many months, so I recently removed it.

    Go figure! Now I don't have an easy way to diagnose if there is a potential issue or if its use error (like shutting down the system with mutil or fidopoll or a MIS BINKP connection, etc) or putting killbusy in a batch file.

    But we'll get to the bottom of it! I've been recently rewriting some Windows side of the code that handles files that potentially have race conditions like this and it seems to have worked really favorably in other areas such as Bink queue files and ghost nodes - so its time to see what I can do with BSY files too.

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/64)
    * Origin: Sector 7 (21:1/108)
  • From PalKat@21:4/137 to g00r00 on Wed Feb 26 11:37:43 2020
    On 26 Feb 2020, g00r00 said the following...

    Thanks. I start with looking into FileToss a bit more as that was the only thing in any sort of recent time that had changes to the BSY file system.

    No not really. The files should be fine on their own and even if they ever did get stuck they should unstick themselves after 2 hours, so something is going on here.

    The only other thing I could think of causing issue is the windows 7 VM. But the server running the VM does not show that VM being power cycled/restarted abruptly let alone during the time fidopoll is locked up busy. That server
    is also my PLEX server so I know its on 24/7 and sits in my office so I know
    no one is messing with it.

    I had a "busylog.txt" active for probably 2 years and in that time no
    one was reporting much of anything to me for many many months, so I recently removed it.

    Go figure! Now I don't have an easy way to diagnose if there is a potential issue or if its use error (like shutting down the system with mutil or fidopoll or a MIS BINKP connection, etc) or putting killbusy in
    a batch file.

    hahaha, go figure...I often tell folks I have the same luck as Homer Simpson and once again this proves it.

    But we'll get to the bottom of it! I've been recently rewriting some Windows side of the code that handles files that potentially have race conditions like this and it seems to have worked really favorably in
    other areas such as Bink queue files and ghost nodes - so its time to
    see what I can do with BSY files too.

    Well I appreciate (like many others) all the work you do on this! And for listening/looking into my current fidopoll issue.

    I will wait with much anticipation for a future release that might help this, in the mean time anything else you need me to look at on my end or you need
    to just let me know.

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
    * Origin: 8-Bit Boyz BBS! -=[ bbs.8bitboyz.com port:6502 ]=- (21:4/137)