From owner-freebsd-questions Tue Jan 13 19:17:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28286 for questions-outgoing; Tue, 13 Jan 1998 19:09:58 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from onyx.atipa.com (user28856@ns.atipa.com [208.128.22.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA20042 for ; Tue, 13 Jan 1998 18:18:37 -0800 (PST) (envelope-from freebsd@atipa.com) Received: (qmail-queue invoked by uid 1018); 13 Jan 1998 04:29:33 -0000 Date: Mon, 12 Jan 1998 21:29:33 -0700 (MST) From: Atipa X-Sender: freebsd@dot.ishiboo.com To: Doug White 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 Precedence: bulk On Mon, 12 Jan 1998, Doug White wrote: > 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 :-) I would love to! That is the desired effect! :-) The problem is that my ttyv1 and v2 were also slammed. The module was the plain old if_de.c. 100MBit is very particular about its cabling, and it kept telling me: enabling 100TX de0 down. Cabling problem? enabling... disabling... blah blah blah ad naseum. If /dev/console was ONLY ttyv0 I'd be the happiest boy alive. Well, certainly one of them :-) Regards, Kevin > 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 > > >