Hello!
We've tried adding a sleep between when the include snippet that changes
the DRAIN_NODE value is written and when we hit `birdc configure`, but
that doesn't appear to make any difference. If we execute `birdc
configure` *twice*, though, everything's fine: The actual exports are
stopped. That's true without any sleep or break between running
configure as well; literally just `birdc configure` back to back in the
script that manages this.
We do not see any indication of issues in the `birdc configure` runs or
in BIRD's logs.
You are not disclosing the version of BIRD you are using. I vaguely
remember that we fixed this kind of bug several years ago where changes
in functions sometimes got ignored.
Thus if you are not using a recent BIRD version, you are probably
hitting that old bug.
Maria
