Hey g00r00,

I've ran into a busy node issue recently sense I've upgraded to a46 and use
the new MIS POLL. I've had nodes become busy that don't seem to resolve themselfs. I've had to use FIDOPOLL KILLBUSY to resolve. Do you have any ideas about possible causes? Does MIS have such a feature?

matt // eggy
Eggy BBS | telnet://bbs.eggy.cc:2300 | ssh://bbs.eggy.cc:2222

--- Mystic BBS v1.12 A46 2020/03/18 (Linux/64)
* Origin: Eggy BBS (77:1/136)

I've ran into a busy node issue recently sense I've upgraded to a46 and use the new MIS POLL. I've had nodes become busy that don't seem to resolve themselfs. I've had to use FIDOPOLL KILLBUSY to resolve. Do you have any ideas about possible causes? Does MIS have such a feature?

I will eventually put KILLBUSY into MIS before I get rid of FIDOPOLL.

The BSY files take (I believe) 4 hours to resolve themselves and they shoudn't ever get stuck unless Mystic is shutdown incorrectly or a crash of course.

That is assuming there isn't something broken.

--- Mystic BBS v1.12 A46 2020/03/22 (Windows/64)
* Origin: Sector 7 (77:1/138)

I will eventually put KILLBUSY into MIS before I get rid of FIDOPOLL.

Alright, sounds good. I'll continue to use FIDOPOLL KILLBUSY as needed.

The BSY files take (I believe) 4 hours to resolve themselves and they shoudn't ever get stuck unless Mystic is shutdown incorrectly or a crash of course.

Not sure if there is something broken.. This didn't clear up in 4 hours, packets were stuck for over 12 hours due to busy nodes before I noticed. It
has happened twice last week. However it hasn't happened at all sense then. Please let me know if I can get you more information.

matt // eggy
Eggy BBS | telnet://bbs.eggy.cc:2300 | ssh://bbs.eggy.cc:2222

--- Mystic BBS v1.12 A46 2020/03/18 (Linux/64)
* Origin: Eggy BBS (77:1/136)