CLI debugging

[micah]

Thanks Pavel,

That works, but I have to say that it is very confusing how those
arguments are presented!

micah

Pavel Tvrdík <pavel.tvrdik at nic.cz> writes:

> Hi, Micah!
>
> It could be a little confusing..
>
> Try in BIRD client this:
>
> BIRD 1.6.0 ready.
> bird> debug all { states }
> bird> debug cogent { states, routes }
>
> Best Regards,
> Pavel
>
> On 2016-08-16 18:06, micah anderson wrote:
>> Hi,
>> 
>> 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 (<protocol> | <pattern> | all) (all | off | { states | routes |
>> filters | interfaces | events | packets })  Control protocol debugging
>> via BIRD logs
>> 
>> BIRD 1.6.0 ready.
>> bird> debug all states
>> syntax error
>> bird> debug all events
>> syntax error
>> bird> debug cogent states
>> syntax error
>> bird> debug cogent events
>> syntax error
>> bird> debug cogent all
>> bird>
>> 
>> The 'all' works, but the others do not. Do I misunderstand the argument
>> option specification?
>> 
>> Thanks,
>> micah