Date: Mon, 19 Mar 2001 09:27:31 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: "Koster, K.J." <K.J.Koster@kpn.com> Cc: freebsd-alpha@FreeBSD.ORG Subject: RE: Syslog reports weird things Message-ID: <15030.5971.45105.874275@grasshopper.cs.duke.edu> In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FD9A6C@l04.research.kpn.com> References: <59063B5B4D98D311BC0D0001FA7E452205FD9A6C@l04.research.kpn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Koster, K.J. writes: > Dear Andrew, > > > > > About the only commonality that I see that your machines have and that > > mine lacks is the xl nic, but I really doubt that's the problem. > > > I have no xl card, I have an fxp card instead. > > > > > Hmm.. What do your /etc/ttys files look like? Specifically, what are > > the settings for the console, vtyv0 and ttyd0 lines. Eg, I have: > > > > console none unknown off secure > > ttyv0 "/usr/libexec/getty Pc" cons25 on secure > > ttyd0 "/usr/libexec/getty std.9600" vt100 on secure > > > My box froze during last week's buildworld. *sigh* It needs a good > scrubbing. :-/ All I can tell you that it has the stock 4.2-release > /etc/ttys with some of the excess virtual terminals disabled. Disable the getty on console & make your system look like above. (getty running on actual device, ttyv0 or ttyd0). This should fix your syslog / dmesg problems. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15030.5971.45105.874275>