[PATCH] feature to keep protocol's state while configuring

[Alexander Zubkov]

And implementation as a separate flag. But I'm not sure here how to
add another parameter to configure command. What I could imagine -
would add multiple numerous combinations and look terrible. And not
sure yet with the naming so it is not too long and not too ambiguous:
keep, keepstate, keeprun, ...?
On Tue, Dec 4, 2018 at 12:21 PM Alexander Zubkov <green at qrator.net> wrote:
>
> The easiest patch would be to implement this behaviour for soft
> reconfig. :) But that is not backward-compatible and might break
> something for somebody. I'm also working on implementing it as
> additional option.
> On Mon, Dec 3, 2018 at 2:51 PM Thomás S. Bregolin <thoms3rd at gmail.com> wrote:
> >
> > Hello,
> >
> > On Wed, Nov 28, 2018, 16:34 Alexander Zubkov <green at qrator.net wrote:
> >>
> >> Hello,
> >>
> >> I have received no feedback on this suggestion and suppose it got
> >> lost. I would be glad to hear some comments about this improvement.
> >> On Fri, Nov 16, 2018 at 4:36 PM Alexander Zubkov <green at qrator.net> wrote:
> >> >
> >> > Hello.
> >> >
> >> > I have created a patch (attached) with new protocol option: disabled
> >> > keep on|off. To keep the protocol's state while loading new config. It
> >> > is useful when protocols disabled manually in the runtime, but we want
> >> > to keep that state when loading new config. Patch is attached. I have
> >> > made it against the current int-new branch.
> >
> >
> > I will second this would be nice to have. I use bird with protocols set to disabled to keep them from coming up at the same time as the daemon, and have actually resorted to a wrapper that changes the configuration file in-place to "disabled no" before doing soft reconfiguration, and then back to "yes".
> >
> > Regards,
> >
> > Thomás
> >
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bird-flag-keep-state.patch
Type: text/x-patch
Size: 3325 bytes
Desc: not available
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20181204/4645fa88/attachment.bin>