From owner-freebsd-questions Mon Sep 30 04:26:50 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA17529 for questions-outgoing; Mon, 30 Sep 1996 03:49:03 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA17425 for ; Mon, 30 Sep 1996 03:48:57 -0700 (PDT) Received: from sdev.blaze.net.au (sdev.blaze.net.au [203.17.53.11]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id WAA19149 for ; Sun, 29 Sep 1996 22:46:11 -0700 (PDT) Received: from localhost (davidn@localhost) by sdev.blaze.net.au (8.7.6/8.6.9) with SMTP id PAA06141; Mon, 30 Sep 1996 15:44:33 GMT Date: Mon, 30 Sep 1996 15:44:31 +0000 () From: David Nugent To: Keith Leonard cc: questions@freebsd.org Subject: Re: messages mess up display In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 29 Sep 1996, Keith Leonard wrote: >I am probably asking a stupid question but - after a lot of work I have >2.1.5 working on my machine (486DX4 with 32megs ram and a 824 meg HD). I >love it (once I caught on to the rationale), however no matter how I log >on (root or keithl (wheel group)) I keep getting these anoying (sp?) >messages about loggings and changes , etc. poping up on the display, which >of course messes up the file (visually) that I'm working on. I realize to >get rid of it (on the screen) I just need to cursor past the message and >back to where I was - BUT PLEEEEASE..... > >Any way to disable this message thingee? Yep. Or redirect them elsewhere. >ps. I have tried compiling the kernel without the system V message option >and I get the same results. Not relevant. These messages are issued by the 'syslog' daemon. You can configure to a find detail where, how and when these messages are issued. The file /etc/syslog.conf is the control file (some of these will have entries that direct to '/dev/console', some of them are directed to 'root'. Most of them will be directed to your log files in /var/log). Don't be TOO heavy handed in removing messages from the console, and I certainly agree that login messages to the console is an overkill. Keep *.alert and *.emerg at least directed to somewhere where it will be seen - they are rare enough, and important enough - that they SHOULD be seen as soon as possible rather than whenever you decide to browse the log. man syslogd man syslog.conf for more information/ David Nugent, Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-791-9547 Data/BBS +61-3-792-3507 3:632/348@fidonet davidn@blaze.net.au http://www.blaze.net.au/~davidn