From owner-freebsd-questions@FreeBSD.ORG Mon Aug 27 17:59:51 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FBAF16A418 for ; Mon, 27 Aug 2007 17:59:51 +0000 (UTC) (envelope-from fatman@crackmonkey.us) Received: from crackmonkey.us (crackmonkey.us [70.58.166.197]) by mx1.freebsd.org (Postfix) with ESMTP id 7966513C442 for ; Mon, 27 Aug 2007 17:59:51 +0000 (UTC) (envelope-from fatman@crackmonkey.us) Received: from [10.22.8.146] (cpc1-swin7-0-0-cust216.brhm.cable.ntl.com [::ffff:86.18.88.217]) (AUTH: PLAIN fatman, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by crackmonkey.us with esmtp; Mon, 27 Aug 2007 11:59:38 -0600 id 0017C49A.46D31110.00006CEC Message-ID: <46D31069.8070107@crackmonkey.us> Date: Mon, 27 Aug 2007 18:56:57 +0100 From: Adam J Richardson User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: blix References: <20070825120018.2F05E16A421@hub.freebsd.org> <1188043958.1307.3.camel@bsdpc.centralamerica> In-Reply-To: <1188043958.1307.3.camel@bsdpc.centralamerica> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: freebsd-questions Digest, Vol 191, Issue 37 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Aug 2007 17:59:51 -0000 blix wrote: > my console and messages file is filling up with these entries: Hi Dan. I hate console spam. Whenever I go to log into my server's ttyv0 [which happens about four times a year], instead of the getty prompt I see reams of out-of-date console errors which I would much rather have vanish into the syslog daemon but somehow don't. I read somewhere about how you can edit syslog.conf to redirect errors to ttyv0 into /var/log/messages, but obviously I misunderstood because it didn't work. Try Googling for syslog.conf howtos, you might have better luck than I did. That error actually looks pretty severe to me. I'd run some diagnostics on da3, like Spinrite for instance. Or just replace da3, if it's something easily replaceable like a USB stick. HtH, Adam J Richardson