From owner-freebsd-questions  Tue Jul  8 15:31:12 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id PAA13086
          for questions-outgoing; Tue, 8 Jul 1997 15:31:12 -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 PAA13069
          for <freebsd-questions@FreeBSD.ORG>; Tue, 8 Jul 1997 15:31:05 -0700 (PDT)
Received: from rhiannon.scsn.net ([208.133.153.146]) by mail.scsn.net
          (Post.Office MTA v3.1 release PO203a ID# 0-32322U5000L100S10000)
          with ESMTP id AAA173; Tue, 8 Jul 1997 18:22:36 -0400
Message-ID: <33C2BF95.5C177BC0@scsn.net>
Date: Tue, 08 Jul 1997 18:30:45 -0400
From: dmaddox@scsn.net (Donald J. Maddox)
Reply-To: dmaddox@scsn.net
X-Mailer: Mozilla 4.01 [en] (Win95; I)
MIME-Version: 1.0
To: chaos@tgci.com
CC: freebsd-questions@FreeBSD.ORG
Subject: Re: (Fwd) garbage from syslogd after compiling new kernel
X-Priority: 3 (Normal)
References: <199707082216.PAA14067@train.tgci.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Riley J. McIntire wrote:
> 
> Hi,
> 
> Could the disabling KTRACE cause the syslog output I got below?
> 
> # KTRACE enables the system-call tracing facility ktrace(2).
> # This adds 4 KB bloat to your kernel, and slightly increases
> # the costs of each syscall.
> #options                KTRACE          #kernel tracing
> 
> Made a new kernel yesterday and am getting this output from syslogd
> now.  AFAIK everything is working...
> 
> config is attached.
> 
> Any suggestions?  And any other criticisms or comments on the config
> would be appreciated...
> 
> Thanks,
> 
> Riley
> 
> /var/log/messages:
> 
> > 1H\^[[m\^[[5;1H\^[[6;1H\^[[m\^[[6;1H\^[[7;1H\^[[m\^[[7;1H\^[[8;1H\^[
> > [m\^[[8;1H\^[[9;1H\^[[m\^[[9;1H\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[
> > 21;1H\^[[m\^[[9;1H\^[[m\^[[7m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[
> 
> \^[[m\^[[23;1H\^[[m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[1m\^[[m\^[[1m\
> ^[[m\^[[9;1H\^[[9;1H\^[[m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[m\^[[23;
> 1H\^[[m\^[[23;1H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[9;1H\^[[m\^
> [[m\^[[1m\^[[m\^[[1m\^[[m\^[[7;1H\^[[1;46H\^[[m\^[[2;1H\^[[m\^[[2;1H\^
> [[3;1H\^[[m\^[[3;1H\^[[4;1H\^[[m\^[[4;1H\^[[5;1H\^[[m\^[[5;1H\^[[6;1H\
> ^[[m\^[[6;1H\^[[7;1H\^[[m\^[[7;1H\^[[8;1H\^[[m\^[[8;1H\^[[
> 
> <snip>
> much more of same
> </snip>
> 
> \^[[4;1H\^[[m\^[[4;1H\^[[5;1H\^[[m\^[[5;1H\^[[6;1H\^[[m\^[[6;1H\^[[7;1
> H\^[[m\^[[7;1H\^[[8;1H\^[[m\^[[8;1H\^[[9;1H\^[[m\^[[9;1H\^[[m\^[[19;1H
> \^[[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...