Re: CLI debugging

Hi. On 2016-08-16 18:06, micah anderson wrote: I wanted to debug the states of a neighbor, but I cannot seem to figure out how to change debugging on the command-line in a way that *seems* according to the argument options: debug ( | | all) (all | off | { states | routes | filters |

Re: CLI debugging

Hi. On 2016-09-02 13:59, Israel G. Lugo wrote: On 08/30/2016 02:01 PM, Bernardo Figueiredo wrote: In my opinion: debug ( | | all) (all | off | ( "{" states | routes | filters | interfaces | events | packets "}" ) ) Control protocol debugging via BIRD logs The parethensis are to group all

Re: CLI debugging

"Israel G. Lugo" writes: > On 08/30/2016 02:01 PM, Bernardo Figueiredo wrote: >> In my opinion: >> debug ( | | all) (all | off | ( "{" states | routes >> | filters | interfaces | events | packets "}" ) ) Control protocol >> debugging via BIRD logs >> >> The parethensis

Re: CLI debugging

On 08/30/2016 02:01 PM, Bernardo Figueiredo wrote: > In my opinion: > debug ( | | all) (all | off | ( "{" states | routes > | filters | interfaces | events | packets "}" ) ) Control protocol > debugging via BIRD logs > > The parethensis are to group all the various options and the "{" and "}" >

Re: CLI debugging

On Wed, 2016-08-24 at 20:16 +0200, Pavel Tvrdík wrote: > On 2016-08-24 19:39, micah wrote: > > > > Thanks Pavel, > > > > That works, but I have to say that it is very confusing how those > > arguments are presented! > > You're welcome! Do you have an idea how to express it another way? In my

Re: CLI debugging

Thanks Pavel, That works, but I have to say that it is very confusing how those arguments are presented! micah Pavel Tvrdík writes: > Hi, Micah! > > It could be a little confusing.. > > Try in BIRD client this: > > BIRD 1.6.0 ready. > bird> debug all { states } > bird>