So I have been running the A45 for a week now and every 2-3 days my fidopoll still gets locked up being busy. After I issue a fidopoll killbusy it resumes just fine for 2-3 days till I have to killbusy again.
fidopoll still gets locked up being busy. After I issue a fidopoll killbusy it resumes just fine for 2-3 days till I have to killbusy again.
So would creating an Event in mystic to run either hourly or daily and
set the Shell of the event to "fidopoll killbusy" be a safe solution?
This issue seems to have gotten more regular over the past few months,
yet nothing has changed on my configuration of the BBS machine.
Are you using [FileToss] by chance? Someone suggesting they think there is actually a problem with that function.
What version of Windows?
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.
Is there something I should be looking for in the logs specific to this? if so which log file?
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.
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.
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 97 |
Nodes: | 16 (0 / 16) |
Uptime: | 00:13:07 |
Calls: | 4,613 |
Calls today: | 7 |
Files: | 8,491 |
Messages: | 349,785 |