Text 30318, 54 rader
Skriven 2012-06-29 13:51:34 av mark lewis (1:3634/12.0)
  Kommentar till text 30309 av Robert Bashe (2:2448/44)
Ärende: binkd (was: Link requ... blah blah)
===========================================
RB> So apparently my suspicion that you can't mix four and five-field node
RB> definitions was correct, although why exactly that should make any
RB> difference as long as the fields are empty is a mystery to me.

 RB> In the meantime, I could confirm that.

that doesn't make sense :(

 RB> I took my binkd.cfg and truncated all the 5-field node descriptions
 RB> to four fields (by deleting the final "-". Then I added _only_ the
 RB> include file from binknod:

[trim]

 RB> This also has only four fields.

 RB> Stopped binkd, started it again with the new configuation. Polled
 RB> Ross to check the behavior with a passworded system.

you don't have to stop binkd... it will see that the configs (yes, even include
ones) have changed and it will (re)load them at the next 60 second idle loop
scan time... then it will dump the old configs from memory another minute later
when it sees they are no longer in use...

 RB> Absolutely no problem. And in particular no error message such as I
 RB> had previously gotten even if _I_ polled a passworded system,
 RB> rather than the reverse.

ok... that's good to hear ;)

 RB> I'm going to let my system run with this new configuation to make
 RB> sure everything is OK, and will report if anything else crops up,
 RB> but it looks like the problem is solved.

 RB> But I _still_ don't understand why an _empty_ field makes so much
 RB> difference in a node description, nor why some people use five
 RB> fields in their configurations and others use four. It would
 RB> interest me if anyone reading this could check their configuration
 RB> to see if the numbers of fields in their node descriptions are
 RB> _mixed_ (some four, some five or even six) and what their
 RB> experience is. 

i might be better to take this discussion over to the binkd support echo...
that's where the real brains hang out who know and work with the code ;) that's
what i did when i saw that my binkd was performing DNS lookups for AKAs of
systems that had called here... even for domains that i am not a member of... i
still don't understand why this is happening but i'm also waiting for the
/release/ version of binkd-1.0 to come down the file distribution pipe... it
was released the other day after a patch was made to lessen the lookups of
those AKA addresses to only once per hour instead of once a minute...

)\/(ark

 * Origin:  (1:3634/12)