From owner-freebsd-questions Mon Jan 12 18:23:22 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA12310 for questions-outgoing; Mon, 12 Jan 1998 18:23:22 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA12302 for ; Mon, 12 Jan 1998 18:23:18 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id SAA22116; Mon, 12 Jan 1998 18:23:11 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Mon, 12 Jan 1998 18:23:11 -0800 (PST) From: Doug White Reply-To: Doug White To: Atipa cc: freebsd-questions@FreeBSD.ORG Subject: Re: syslog-free console/vty possible? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 5 Jan 1998, Atipa wrote: > > You are right, since I killed syslog and it still came up. Is there a way > to restirct /dev/console to only ttyv0 or something? That would be perfect. /dev/console is ttyv0 by default. I wasn't aware you could rewire it. Why not use vty1 instead? that's what we do; we just leave the console on vty1 and let the messages pile up on vty0, checking them every so often. That way it lets the screensaver kick in :-) Some messages are rerouted to root logins by syslogd. kernel printf's are probably in that department. Is that what you mean? > I even tried somethings to the affect of: > # cat < /dev/console > /dev/null & > but they did not do the trick. I could have rm'ed /dev/console, and > linked it to a real file, but that would be a bit too harsh. I would be very careful removing /dev/console; it has a unique major/minor number (0,0) so I suspect it's something special. > I would think there would be something in either /etc/ttys, or possibly > the syscons source code. Or the source of the offending module. I assume you're getting pummeled with ipfw messages? Just go into ipfw (sys/i386/isa/ipfw_* I think) and comment out the printf's then rebuild & reinstall the kernel. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major