From: Pavel Bykov (slidersv@gmail.com)
Date: Mon Feb 02 2009 - 12:53:42 ARST
Good chance to stop it is to telnet from another device - then you can stop
it unless you overloaded CPU with debug.
If you don't know "to debug or not to debug" because of possible message
flood, you can do: "logging buffered 128000 7" and "logging console info",
then you won't have debug in the console, but only in "show logging".
This is good CPU saving trick which I use in production (CPU usage is
enormously reduced when output to the console is not required), but it
requires to either clear logging or use of pipe to find what you need. Pipe
with time is one of the ways.
On Mon, Feb 2, 2009 at 12:28 PM, hanan <nouran@skynet.be> wrote:
> Hi
>
>
>
> Can anyone tell me how to stop an out of control scrolling debug. I know
> the
> command is undebug all, but I can't seem to type it in as it's scrolling so
> fast,
>
> I am doing this over a console cable (access server) and not telnet
>
> I tried u all, and I type undebug all on notepad and past it there but no
> hope until I shut the interface in SW which is connecting to this router.
>
>
>
> Thanks
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
-- Pavel Bykov ---------------- Don't forget to help stopping the braindumps, use of which reduces value of your certifications. Sign the petition at http://www.stopbraindumps.com/Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:44:09 ARST