Date: Thu, 12 Nov 1998 09:51:53 -0500 (EST) From: Tim Allman <tim@softpulse.com> To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: bin/8666: X blocks serial port with getty process on it Message-ID: <199811121451.JAA00653@sherman.softpulse.com>
next in thread | raw e-mail | index | archive | help
>Number: 8666
>Category: bin
>Synopsis: X blocks serial port with getty process on it
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Nov 12 07:00:00 PST 1998
>Last-Modified:
>Originator: Tim Allman
>Organization:
SoftPulse Software
>Release: FreeBSD 2.2.7-RELEASE i386
>Environment:
>Description:
When the OS is booted up without X all is well. The following line in
/etc/ttys does exactly what it should. That is it allows logins on the
serial port.
cuaa3 "/usr/libexec/getty std.115200" vt100 on secure
However, when X is started either through startx or xdm this port is blocked.
Logins are impossible and a current user is prevented from using the port.
The problem remains until the next reboot.
Interestingly, the modem, setup using the following line is not affected
by X at all.
modem "/usr/libexec/getty std.115200" dialup off insecure
>How-To-Repeat:
Boot up without X. Logins through cuaa3 work properly. Start X using startx
on a console virtual terminal. Serial port is now blocked. Killing X does
not help.
>Fix:
???
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811121451.JAA00653>