Is enabling the “bgp log-neighbor-changes” a good idea? Or do we worry about some low end system where this change suddenly fills up the disk/flash/ramdisk ?
- Martin On 21 Oct 2015, at 6:42, Daniel Walton wrote: > Signed-off-by: Daniel Walton <[email protected]> > Reviewed-by: Donald Sharp <[email protected]> > --- > bgpd/bgpd.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/bgpd/bgpd.c b/bgpd/bgpd.c > index 400e2a3..1a10c2e 100644 > --- a/bgpd/bgpd.c > +++ b/bgpd/bgpd.c > @@ -1971,6 +1971,7 @@ bgp_create (as_t *as, const char *name) > bgp->default_keepalive = BGP_DEFAULT_KEEPALIVE; > bgp->restart_time = BGP_DEFAULT_RESTART_TIME; > bgp->stalepath_time = BGP_DEFAULT_STALEPATH_TIME; > + bgp_flag_set (bgp, BGP_FLAG_LOG_NEIGHBOR_CHANGES); > > bgp->as = *as; > > @@ -5256,8 +5257,8 @@ bgp_config_write (struct vty *vty) > VTY_NEWLINE); > > /* BGP log-neighbor-changes. */ > - if (bgp_flag_check (bgp, BGP_FLAG_LOG_NEIGHBOR_CHANGES)) > - vty_out (vty, " bgp log-neighbor-changes%s", VTY_NEWLINE); > + if (!bgp_flag_check (bgp, BGP_FLAG_LOG_NEIGHBOR_CHANGES)) > + vty_out (vty, " no bgp log-neighbor-changes%s", VTY_NEWLINE); > > /* BGP configuration. */ > if (bgp_flag_check (bgp, BGP_FLAG_ALWAYS_COMPARE_MED)) > -- > 1.7.10.4 > > > _______________________________________________ > Quagga-dev mailing list > [email protected] > https://lists.quagga.net/mailman/listinfo/quagga-dev _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
