Subj : Re: MUTIL
To   : Nazferiti
From : The Godfather
Date : Wed Aug 12 2020 10:14:53

 Na> It seems that once a "busy" node is encountered,  all nodes that are
 Na> polled after are also "busy".  They can be polled individually or if you
 Na> just wait a few minutes the issue seems to resolve itself.
 Na> 

Thanks Mike.  I had been polling individually, however once I got past
(I think) 5 networks on my system .. the event editor started acting
wonky.  I would set up a new network to poll at a specific time, exit
config, and a day later would not see any messages coming through.  I'd
load event editor, and sure enough the event I created disappeared as
well as a few previous networks duplicated, resulting in them being
polled twice.  So Stizzed assisted me in setting up a batch file which
works better, as it's now just one event .. however now the fidokill
..bsy is necessary as I get the mutil .bsy error.  I haven't seen it
resolve on it's own without fidokill busy though .. you're lucky there.
What has been slightly helpful is making the largest traffic networks
poll last within the batch file.  I may even split the batch file into
two, to reduce how much mutil is being asked to process at one time.  
I know it's probably just an extra step, but it's worth a shot and
can't hurt anything.  But if it's not the version change that caused
the issue ..... I wonder if it's the number of networks?  

-tG

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
 * Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

.