On 3/5/19 11:24 AM, Alarig Le Lay wrote:
>
> The client doesn’t care about the configuration file, only about the
> socket.
Oh, sorry, I was reading the wrong part of the man page.
It looks like you *can* specify which config file to check, but in a
different way:
configure check ["config file"]
Read and parse given config file, but do not use it. useful for
checking syntactic and some semantic validity of an config file.
So you'd want something like "configure check ${CONF_FILE}" I guess.
That way if you ever have two instances of bird running, reloading the
second instance won't check the config file for the first instance.
And "-r" was a good idea.
