Re: xdm, was Re: Accepting external sendmail on 2.0.2

From: Frederick Bruckman (fredb_at_immanent.net)
Date: 07/20/05 

Date: Wed, 20 Jul 2005 11:25:41 -0500

In article <dbgo31$n3d$1@string1.ciencias.uniovi.es>,
        Igor Sobrado <igor@string1.ciencias.uniovi.es> writes:
>
> (the only uncommented line has vt05 in the default file, no need
> to write a modified version of this file in /etc/X11). From your
> post, I understand that the race condition occurs only when the
> X server starts too fast and uses one of the (yet) unassigned
> virtual consoles that will be requested by wscons as soon as
> it starts. Well, I do no think that it will happen now, as the
> console to be used (vt05) is in the xdm's Xservers configuration file.

OK.

> The problem, though, is that both the text console (ttyE0, but
> labeled "console") and the xconsole automatically started by
> xdm are in some way "incompatible".

I think, if you comment out "console" and enable the getty on
"ttyE0" instead, that may fix your problem. With that, "xconsole"
should still get the kernel messages, but not interfere with the
getty on ttyE0.

> To be exact, all works fine until someones tries to login in the
> text console. When someone goes to the text console and tries
> to login to the system the next message appears in the small
> console window started by xdm:
>
> -------------------------------
> Console log for altair.v6.local
> s
> NetBSD/i386 (altair.v6.local) (console)
>
> login: Jul 18 18:38:55 altair init: getty repeating too quickly on port /dev/console, sleeping
> -------------------------------
>
> (the "s" in the second line is the first character in my login name)
> and the text console "hangs". After a given amount of time
> (usually 5 or 10 minutes) the text console can be used to log into
> the system (at least when X has been started and there is not an
> xconsole running, not sure if that process has been killed or died). 

-- 
Frederick

Relevant Pages

  • Newbie: Writing console messages to a file FC2 2.6.5
    ... I am guessing these are kernel error messages. ... The kernel messages are directed to the console ... # Logging much else clutters up the screen. ...
    (Fedora)
  • Re: Newbie: Writing console messages to a file FC2 2.6.5
    ... > I am guessing these are kernel error messages. ... > The kernel messages are directed to the console ... > # Logging much else clutters up the screen. ...
    (Fedora)
  • Re: Bothering error message when logging out X
    ... other kernel messages (e.g. like when you plug in a USB device)? ... so to stop low-level messages on console, and that bothering message did not ... How can I avoid this as well, and all undesired kernel messages? ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • Re: stop kernel messages from splashing on the console
    ... I am getting these kernel messages on the consoles which I want to avoid ... From the man pages it is not clear to me if syslog actually handles the internal kernel messages going to the console, there is also klogd, and I know internal messages still make it to the console even when userspace is screwed up badly, so I would suspect that the klogd thread in the kernel is handling it. ...
    (Fedora)
  • Re: changing debuglevel of kernel messaging going to console
    ... > now all kernel messages are printed to system console by default: ... > There is a problem that in case of a serial console, ... > sending bogus ARP replies. ... > FreeBSD box with serial console may lead to a DoS like conditions. ...
    (freebsd-current)