From: Christopher Van Heuveln (cvanheuv@xxxxxxxxx)
Date: Wed Aug 09 2000 - 11:46:33 GMT-3
5000 is not that big. I usually set it to 65535.
On Wed, Aug 09, 2000 at 10:15:49AM -0400, Brian Hescock wrote:
> Perry,
> I've recently heard of one or two specific debug commands that give you
> this functionality but it's only for those specific debug commands, it
> won't turn off all debugs after that time period (I don't know which
> specific debugs they are). As a workaround you can minimize the impact
> of the debugs by:
>
> - term no mon
> - no logging console (config mode)
> - logging buffered 5000 (config mode)
>
> Do a "show log" to see your debug output.
>
> You could also do a timed reload of the box to kill the debugs... say
> after 20 seconds... just kidding ;-) Have a good one,
>
> Brian
>
> On Wed, 9 Aug 2000, cpchang wrote:
>
> > Guys:
> > We all know when debug something in router, it may cause
> > the router output so many messages and use many CPU resource too.
> > So, I am just wondering is there any command that can turn OFF the
> > debug command in a schedule timing, for example 20 seconds later,
> > then turn off the debug itself. That would be very helpful.
> >
> > Best regards
> >
> > Perry Chang
> > Engineer of NetStar Taiwan
> > Email: cpchang@altavista.net
> > Office:+886-2-27405052 FAX: +886-2-2740-1949
> > 12F, 58, Fu-Hsing N. Rd., Taipei, Taiwan/ Zip:104
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:23 GMT-3