[Xorp-hackers] Old bug entries

[Pavlin Radoslavov]

> I would like to see #199 commited to CVS and I
> will open up a bug report soon just as I'm sure I
> have looked through all the previous. Don't want
> to create a duplicate.

Your patch for #199 looks good, so I will try to double-test and
commit it relatively soon.

> Anyway my current problem lies in that my
> configuration contains:
>         bgp {
>             bgp-id: 195.182.5.253
>             local-as: 39525
>             peer "217.10.127.13" {
>                 as: 35706
>                 next-hop: 217.10.127.13
>                 local-ip: "217.10.127.14"
>             }
>         }
> but xorp_bgp seems to have crashed.
> I would now like to do a 'commit full' so that bgp
> is restarted. I do not want to loose OSPF
> connectivity (ie, don't restart entire XORP) so
> currently my only solution seems to be to delete
> the bgp part of the configuration and readd it
> again.
> 
> Anyway, as stated I think the commit command
> should be available all the time, as suggest by
> #199.

I agree about #199 alone, but "commit full" just to restart BGP may
be confusing. A command like "restart bgp" or "restart protocols
bgp" might be more intuitive.

Pavlin