Hi Robert.

04 Sep 16 13:28, you wrote to me:

 RB> Tommi Koivula wrote to Robert Bashe on Sunday September 04 2016 at 12:18:

 TK>>> passwords ~/ftn/binkd/passwords

 TK>> And if you are not sure in which order the included files are
 TK>> interpreted, you can run binkd -d to check. ;)

 RB> My understanding is that binkd.cfg is read from top (beginning) to bottom
 RB> (end), and that entries at the bottom overwrite any before them.

 RB> So I would assume any include files are read in the same order: the last
 RB> one listed in binkd.cfg takes prescedence over any include file listed
 RB> previous to it.

My understanding was that the later setting will replace the previous setting
if it was not set when reading the conf from top to bottom. So that if any of
the setting is "-" it may be replaced. Also my understanding was that the
password in passwords.lst has the top priority, but I'm not sure anymore.

I made a little test:

=== binkd.cfg: ===
passwords passwords.lst
node 2:2448/44 ip1.localnet pass1 h
node 2:2448/44 ip2.localnet pass2 c
node 2:2448/44 ip3.localnet pass3 i
=== binkd.cfg: ===

=== passwords.lst ===
password 2:2448/44  pass4
=== passwords.lst ===

And the result of 'binkd -d binkd.cfg':

2:2448/44@fidonet    ip3.localnet pass1 i - -

Pretty weird...

'Tommi

---