From owner-freebsd-questions  Tue Jul  8 17:28:27 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id RAA19376
          for questions-outgoing; Tue, 8 Jul 1997 17:28:27 -0700 (PDT)
Received: from mail.scsn.net (scsn.net [206.25.246.12])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA19370
          for <freebsd-questions@FreeBSD.ORG>; Tue, 8 Jul 1997 17:28:24 -0700 (PDT)
Received: from rhiannon.scsn.net ([208.133.153.154]) by mail.scsn.net
          (Post.Office MTA v3.1 release PO203a ID# 0-32322U5000L100S10000)
          with ESMTP id AAA132; Tue, 8 Jul 1997 20:19:56 -0400
Received: (from root@localhost)
	by rhiannon.scsn.net (8.8.6/8.8.5) id UAA00346;
	Tue, 8 Jul 1997 20:28:10 -0400 (EDT)
Message-ID: <19970708202810.32672@scsn.net>
Date: Tue, 8 Jul 1997 20:28:10 -0400
From: "Donald J. Maddox" <dmaddox@scsn.net>
To: chaos@tgci.com
Cc: freebsd-questions@FreeBSD.ORG
Subject: Re: (Fwd) garbage from syslogd after compiling new kernel
Reply-To: dmaddox@scsn.net
References: <199707082316.QAA14509@train.tgci.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.76
In-Reply-To: <199707082316.QAA14509@train.tgci.com>; from Riley J. McIntire on Tue, Jul 08, 1997 at 04:18:38PM +0000
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, Jul 08, 1997 at 04:18:38PM +0000, Riley J. McIntire wrote:
> 
> > Riley J. McIntire wrote:
> > > 
> > > Hi,
> > > 
> > > Could the disabling KTRACE cause the syslog output I got below?
> 
> snip
> 
> > > \^[[m\^[[20;1H\^[[m\^[[21;1H\^[[m\^[[2;1H\^[[m\^[[7m\^[[m\ > wdc0:
> > > disabled, not probed. > ccd0-3: Concatenated disk drivers
> > 
> >     This looks like the kind of stuff (cursor control sequences, etc.)
> > that
> > doing a visual userconfig might leave in your logs...
> > 
> That's most likely it--I used it right after rebuilding this kernel.  
> 
> I was kinda concerned about disabling KTRACE but couldn't find a 
> reason not to.  Is there any reason to enable it for "normal" use?  
> It *is* enable by default, as are a number off other required 
> "options".

    As far as I know, there is no reason why you should _need_ KTRACE,
but I recommend keeping it.  When a program is doing unexpected things,
the output of 'ktrace -i <prog>; kdump | more' can be very informative...