On Wed, Sep 30, 2020 at 1:46 PM Bernd Naumann <[email protected]> wrote: > > Hi Alexander, > > I'm confused: "configure soft ["<file>"] [timeout [<sec>]] Reload > configuration and ignore changes in filters" > > So (new/modified) filters are loaded or not? Or just not yet applied? > (In contrast to plain `configure`)
Yes, "configure soft" just loads new filters, but they are applied to new route updates only. Plain "configure" will reload/restart protocols automatically if the filters were updated (as far as I know). > > > Because when the > > filter is changed, routes are not reevaluated. The new filter will > > only affect newly arriving routes. > > If I have modified i.e. the filter used for export on protocol kernel, I > would do > configure soft > restart kernel1 > > to re-load the filter config and then restart kernel1 and do re-evaluate > all routes, correct? Yes, correct. If you want to reload only kernel1, better use configure soft. > > > > On 30.09.20 12:54, Alexander Zubkov wrote: > > Hi, > > > > No, reload/restart changes the state of the protocol in the context of > > currently loaded configuration. If you change your configuration, you > > need to do configure/"configure soft" first to update filters. And > > probably reload protocols after that if needed. Because when the > > filter is changed, routes are not reevaluated. The new filter will > > only affect newly arriving routes. > > > > On Wed, Sep 30, 2020 at 11:49 AM Bernd Naumann <[email protected]> wrote: > >> > >> Hi *, > >> > >> Again, I have "such" a question... > >> > >> If I can reload (or restart) a single protocol, would that also re-read > >> the filter used for that protocol? > >> > >> Or would do I need `configure` anyway? > >> > >> Thanks again! > >> Bernd >
