Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!lucy.cc.swin.edu.au!news.rmit.EDU.AU!news.unimelb.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!news.maxwell.syr.edu!news.cis.ohio-state.edu!opus.anet-stl.com!forbidden-donut.anet-stl.com!doogie From: doogie <doogie@forbidden-donut.anet-stl.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: strange kernel log messages .... Date: 10 Jul 1997 17:08:22 GMT Organization: Western Pacific Network Services Lines: 36 Message-ID: <5q34u6$pah$3@opus.anet-stl.com> References: <33C48FAE.3FFC@polito.it> NNTP-Posting-Host: forbidden-donut.anet-stl.com X-Newsreader: TIN [UNIX 1.3 unoff BETA 970527; i386 FreeBSD 3.0-CURRENT] Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:44225 Paolo Tealdi <tealdi@polito.it> wrote: > I have a 2.2.1 RELEASE system that every morning send me the > security check output mail. > The kernel log alwais report this strange sequence of escapes > characters .... > Somebody can tell me what they are ? > [8;1H\^[[m\^[[8;1H\^[[9;1H\^[[m\^[[9;1H\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21;1 > H\^[[m\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21;1H\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[ > m\^[[21;2H\^[[m\^[[9;1H\^[[m\^[[7m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[1m\^[[m\^ > [[1m\^[[m\^[[9;1H\^[[9;1H\^[[m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[1m\^[[m\^[[1m > \^[[m\^[[9;1H\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21;1H\^[[m\^[[m\^[[19;1H\^[[m\ > ^[[20;1H\^[[m\^[[21;1H\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21;2H\^[[m\^[[8;1H\^[ > [m\^[[7m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[8;1H\^[[8;1H\ > ^[[m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[8;1H\^[[m\^[[19;1 > H\^[[m\^[[20;1H\^[[m\^[[21;1H\^[[m\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21;1H\^[[ > m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21;2H\^[[m\^[[7;1H\^[[m\^[[7m\^[[m\^[[23;1H\^[[ > m\^[[23;1H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[7;1H\^[[7;1H\^[[m\^[[m\^[[23;1H\^[[m\^[ > [23;1H\^[[m\^[[1m\^[[m\^[[1m\^[[m\^[[7;1H\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21 > ;1H\^[[m\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21;1H\^[[m\^[[19;1H\^[[m\^[[20;1H\^ > [[m\^[[21;2H\^[[m\^[[6;1H\^[[m\^[[7m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[1m\^[[m > \^[[1m\^[[m\^[[6;1H\^[[6;1H\^[[m\^[[m\^[[23;1H\^[[m\^[[23;1H\^[[m\^[[1m\^[[m\^[[ > 1m\^[[m\^[[6;1H\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21;1H\^[[m\^[[m\^[[19;1H\^[[ > m\^[[20;1H\^[[m\^[[21;1H\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21;2H\^[[m\^[[5;1H\ > Really beautiful .... If you boot into the kernel configuration (-c at the boot prompt) it throws some garbage into the kernel message list. I believe it's all the ansi positioning code and such. If you don't boot like that, you wont' get all that. -- Jason Young ANET Technical Staff