On Tue, Oct 29, 2013 at 03:37:51PM +0800, Gao feng wrote: > Now, /dev/console is linked to the /dev/pts/0, > so for the process agetty, the tty device of > agetty is pts/0. this will cause login container > failed. > since pts/0 is not in the /etc/securetty. so > pam module pam_securetty will prevent the root > user logging on the system. > > this patch doesn't make /dev/console a symbol but > binds /dev/pts/0 to it. so the tty device of > agetty will be console. root can login the system > successfully. This only really fixes it for the first console. If the guest has multiple <console/> lines defined, we still have the same problem with securetty for other consoles. I'm wondering if there is any scope for just getting the securetty check todo the right thing by default for psuedo ttys. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list