Subj : Problems with events run
To   : Sean Dennis
From : mark lewis
Date : Sat Feb 26 2011 11:09 am


 ML> Chuckle.  So don't forget to erase the flag points on your hard drive
 ML> after you play this cool stunt and they are no longer needed..

 SD> What I may simply do is this: write a quickie Pascal program that
 SD> monitors for the existance of a semaphore then calls up the BBS
 SD> nodes to restart.  It's fairly simple to do.  I just have to do it.
 SD> I did learn a bit though about dealing with Maximus and its events
 SD> file though.

is there not a semaphore that you can write to have MAX simply exit and then 
catch that in a loop in the .BAT file?

another thought would be something like what i do with my FD nodes and that is 
that they all exit via an event with a specific errorlevel... like my 
suggestion above, i catch that and simply loop the .BAT file until another 
semaphore is removed...

trying to clarify...

my main node that does the maint exits with an errorlevel and create a 
maint.sem semaphore... then it loops until all of the other nodes have exited 
and created or removed their "i'm up" semaphore files... the other nodes then 
loop until the maint.sem semaphore is removed... when the main node sees that 
all the other nodes are down, then it runs the maint and the last thing done is 
to remove the maint.sem semaphore before reloading to the top of the .BAT... 
all the other nodes jump to the top of the .BAT for their restart, too...

the problem may be the semaphores and exit errorlevels that you can access and 
catch, though...

)\/(ark

 
* Origin:  (1:3634/12)

.