Path: utzoo!attcan!uunet!van-bc!ubc-cs!news-server.csri.toronto.edu!utgpu!cunews!bnrgate!bwdls56!fortinp
From: fortinp@bwdls56.bnr.ca (Pierre Fortin)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: 8.1(14) debug locks up router
Summary: More "logging" confusion...
Message-ID: <1990Oct15.185353.5499@bnrgate.bnr.ca>
Date: 15 Oct 90 18:53:53 GMT
References: <1990Oct15.164223.25730@bnrgate.bnr.ca> <1990Oct15.171333.28849@bnrgate.bnr.ca>
Sender: news@bnrgate.bnr.ca (USENET News System)
Organization: Bell-Northern Research, Ltd. Ottawa Ontario CANADA
Lines: 23

In article <1990Oct15.171333.28849@bnrgate.bnr.ca>, fortinp@bwdls56.bnr.ca (Pierre Fortin) writes:
> Hmmm... I just checked the configuration in one of the routers which suffered
> a disastrous logical fate.  The router is setup with "logging on" which is
> the default.  I entered the command and checked the config just to be sure.
> The manual reads: "The _logging on_ subcommand enables message logging to all
> destinations except the console."
>  
> Is there a bug here?  Why was the real console outputting debug messages if
> the manual is correct and the router was defaulting to *not*(?) send output
> to the real console?

Sorry, I should have included this in my previous posting:

The "show logging" command reports "Syslog logging: enabled" when "logging on"
is set; and "Syslog logging: disabled" when "no logging on" is set.  It's 
nice to know that the messages work :^)

Ciao.

Pierre Fortin       Bell-Northern Research     I know, my postings are
Internet Systems    P.O.Box 3511, Stn C        terse and humourless. So?
(613)763-2598       Ottawa, Ontario            RIP: aptly named protocol
fortinp@bnr.ca      Canada    K1Y 4H7          AppleTalk: Adam&Eve's design