> Hello Wilfred,
> On 13 Oct 16 17:45, Wilfred van Velzen wrote to Nicholas Boel:
>>> So lately I've been seeing some odd logging when starting binkd
>>> or when it automatically restarts after a config change:
>>> Cannot find domain for zone 2, assuming 'fidonet'
>>> Cannot find domain for zone 3, assuming 'fidonet'
>>> Cannot find domain for zone 4, assuming 'fidonet'

  Do/did you have those zones defined in the config?  (Thought the default
config already had those...)


>>> These are repeated multiple times for each. Obviously I
>>> understand that I don't have a zone 2, 3, or 4 address, but I do
>>> have links in those zones. And I understand this is not breaking
>>> anything. It's more of an annoyance than anything. Hundreds of
>>> these log entries every time upon config change or startup just
>>> seems like it could be avoided somehow.
>>> Is there any way to specify that zones 1-4 all fall under the
>>> 'fidonet' domain so I don't get these errors in my logs?

  Define them in the same way that zone 1 (in your case) is defined.


>> Since you see hundreds, I think you are using a BINKD.TXT that has the
>> nodes listed without the '@fidonet' part. So no 5D addresses. Which
>> causes binkd to generate those warnings when it reads the file, and
>> comes across nodes in different zones than your default.

   As far as I know I'm using the same version of the Binkp node extractor that
I was before, but I'll be going over every thing after I get all of my stuff
out of storage.




Jame







--- BBBS/Li6 v4.10 Dada-1