On 1/28/19 4:18 PM, Ondrej Zajicek wrote:
>> I would like to suggest to change the default name of the configuration file
>> for
>> bird version 2.0.
[...]
> Well, workaround would be to have config files in separate files and
> /etc/bird.conf just a symlink, which can be simply changed after p
On Sat, Jan 26, 2019 at 02:55:29PM +0100, Eugene Crosser wrote:
> Hello,
>
> I would like to suggest to change the default name of the configuration file
> for
> bird version 2.0.
Hello
We noticed the issue when working on Debian packages for BIRD 2.0.
Renaming the config file in upstream is no
I can suggest changing it so: bird 2 would try to open new config
file, say, bird2.conf and only if there's no such a file, would fall
back to bird.conf.
--
End of message. Next message?
On 26/01/2019 15:26, Christoffer Hansen wrote:
> On 26/01/2019 14:55, Eugene Crosser wrote:> I would like to suggest to
> change the default name of the configuration file for
>> bird version 2.0.
> Wouldn't using the -c switch[0][1] to give the bird daemon a
> /path/to/my/bird-1.6/bird.conf , /pa
On 26/01/2019 14:55, Eugene Crosser wrote:> I would like to suggest to
change the default name of the configuration file for
> bird version 2.0.
Wouldn't using the -c switch[0][1] to give the bird daemon a
/path/to/my/bird-1.6/bird.conf , /path/to/my/bird-2.0/bird.conf be
sufficient?
[0]: https:
Hello,
I would like to suggest to change the default name of the configuration file for
bird version 2.0.
The two bird versions cannot use the same file because of syntax change. And
some of us distribute the file via configuration management tools (like ansible
etc.). This makes upgrade path rat
