Date: Mon, 12 Jan 1998 18:23:11 -0800 (PST) From: Doug White <dwhite@gdi.uoregon.edu> To: Atipa <freebsd@atipa.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: syslog-free console/vty possible? Message-ID: <Pine.BSF.3.96.980112182002.22079G-100000@gdi.uoregon.edu> In-Reply-To: <Pine.BSF.3.91.980105204802.307A-100000@dot.ishiboo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980112182002.22079G-100000>