On Mon, 22 Feb 2021 at 19:34, ico wrote: > But using symlinks sounds better than overwriting config files.
Depends partly on your preference, too. Using one large config file. And updating a symlink to do dst=bird_202002231200.conf src=bird.conf rm $src ln -sr $src $dst Is one way. Another would be to split it out into smaller chunks. With the main bird.conf file rarely changing. And mostly everything in the included files is what changes. E.g. each BGP peer is configured in a sub-dir, and one-file-per-BGP-peer. ./peers/$peer.conf Your approach is your own to decide! When changing the bird.conf files. You have to force a reload first regardless. Before BIRD daemon re-reads the conf file from the disk. (+ preferable running a bird -c configure check ["config file"] first [0], to verify the conf file to be reloaded is valid) [0]: https://bird.network.cz/?get_doc&v=20&f=bird-4.html -- Chriztoffer
