Subj : binkley.evt
To : Kevin Klement
From : Mike Tripp
Date : Sat May 14 2005 10:52 pm
Hello Kevin!
14 May 05 14:36, Kevin Klement wrote to Mike Tripp:
KK> Hi Mike,
KK> I'm down to a "bare-bone's" binkley.evt, this is gotta fix the dialing
KK> out to HOLD nodes, how's it look to you?
Yes...I'm all for trying a pared down version. You're using a lot of flags
that I haven't messed with and looks like my doc file is corrupt after ten
years on the Netware server and I'm going to need to go scrounge a fresh copy
to play in the deep end.<g> I've started to try to duplicate your setup a time
or two to test and am reminded of how much more non-trivial that is than it
sounds.
You still have the 10AM Sat zero-length forced event ahead of your everyday 4AM
to midnight event...so resequence to ascending order. The overlap might be
causing the Event# confusion.
I still don't think the dialout is Bink's issue...but the fact that the hold
node's file is not .HLO is. If you still had the problem with the resorted
ROUTE.CFG, then I think it may necessarily Squish either, but perhaps some more
code later in your batch that might be running when you think it isn't. Is it
only doing it for this one node, or is it just lucky that this is the guy with
something still pending at midnight?
P.S. My equivalent trick to your scripts to keep the analog node from dialing
my IP nodes is to assign them my analog number as an override in the analog
BINK.CFG. That kept the analog side from trying to CRASH the same node that
BINKD was trying to crash, but since it is configurable by address, I could
still have the analog node dial Seaborn if nothing was happening on the IP
side...due to issues at either end.
