getty acting strange
I have two machines running the latest Debian/unstable that are having getty
problems.
One machine is running 2.6.0-test11 and has gettys on VT's tty2, tty3, and
tty4 failing with the message:
"failed to query next available vt", this occurs from the following code in /
agetty.c:
if ((fd = open("/dev/console", O_WRONLY, 0) ) < 0 )
error(_("/dev/console: cannot open: %m"));
do
{
if ((ioctl(fd, VT_OPENQRY, &newvtno ) < 0))
error(_("failed to query next available vt"));
Here's the relevant section of strace output:
open("/dev/console", O_WRONLY|O_LARGEFILE) = 1
ioctl(1, 0x5600, 0xbffff7c8) = -1 EINVAL (Invalid argument)
ls -l /dev/console
crw--w---- 1 root tty 5, 1 Dec 24 02:48 /dev/console
The other machine when running 2.6.0-test11 and 2.6.0 has a problem whereby
after logging out from a VC the next getty process that init spawns regards
the terminal as still being in use, there is a delay of a minute or so until
a login prompt appears on that VC.
Any ideas on what these could be?
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
Reply to: