Subj : FastEcho + BinkD
To   : Tony Langdon
From : mark lewis
Date : Fri Apr 06 2018 04:58 pm

 On 2018 Apr 06 19:57:00, you wrote to me:

 ml>> why? just fix the domain line in your binkd.cfg file so it points to
 ml>> the all caps directory instead of the lower case one... oh, wait...
 ml>> FE tacked on the zone extension, too?? hummm... binkd should support
 ml>> that... what are your domain lines in your binkd.cfg?

 TL> Looks like Fastecho works like mutil (Mystic) and SBBSecho.  The fix
 TL> is simple. The default zone should be the same as the primary address
 TL> for all AKAs in binkd.conf.  Then binkd will look in the correct place
 TL> for the outbound files.

that's what i'm thinking, too... i didn't realize that FE was fully 5D... i'm
kinda confused, too, by what seems to be the report saying that binkd would
look in out/retronet but FE was creating out/retronet.050... BSO is hard,
man... :lol:

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
.... Law of Combat: No inspection-ready unit has ever passed combat.
---
 * Origin:  (1:3634/12.73)

.