From owner-freebsd-questions  Tue Jul  8 21:12:02 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA25605
          for questions-outgoing; Tue, 8 Jul 1997 21:12:02 -0700 (PDT)
Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA25581
          for <freebsd-questions@FreeBSD.ORG>; Tue, 8 Jul 1997 21:11:45 -0700 (PDT)
Received: from sweden.it.earthlink.net (sweden-c.it.earthlink.net [204.250.46.50])
	by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id VAA07765
	for <freebsd-questions@FreeBSD.ORG>; Tue, 8 Jul 1997 21:11:40 -0700 (PDT)
Received: from rjmcintire (pool059-max5.la-ca-us.dialup.earthlink.net [207.217.4.134])
	by sweden.it.earthlink.net (8.8.5/8.8.5) with SMTP id VAA09114;
	Tue, 8 Jul 1997 21:10:58 -0700 (PDT)
Message-Id: <199707090410.VAA09114@sweden.it.earthlink.net>
Comments: Authenticated sender is <rjmcintire@mail.earthlink.net>
From: "Riley J. McIntire" <rjmcintire@germany-c.it.earthlink.net>
Organization: RJM Consulting
To: dmaddox@scsn.net, freebsd-questions@FreeBSD.ORG
Date: Tue, 8 Jul 1997 20:58:11 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: (Fwd) garbage from syslogd after compiling new kernel
Reply-to: rjmcintire@wilshire.net
CC: freebsd-questions@FreeBSD.ORG, rjm@wilshire.net
Priority: normal
X-mailer: Pegasus Mail for Win32 (v2.42a)
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> From:          "Donald J. Maddox" <dmaddox@scsn.net>
> 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...

Aha!  Thanks again for the info.

Riley