Date: Tue, 8 Jul 1997 20:58:11 +0000 From: "Riley J. McIntire" <rjmcintire@germany-c.it.earthlink.net> To: dmaddox@scsn.net, freebsd-questions@FreeBSD.ORG Cc: freebsd-questions@FreeBSD.ORG, rjm@wilshire.net Subject: Re: (Fwd) garbage from syslogd after compiling new kernel Message-ID: <199707090410.VAA09114@sweden.it.earthlink.net>
next in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199707090410.VAA09114>