PAM breakage
Jens Schweikhardt
schweikh at schweikhardt.net
Sat May 14 05:22:38 PDT 2005
On Sat, May 14, 2005 at 03:25:13PM +0800, Tai-hwa Liang wrote:
# On Sat, 14 May 2005, Daniel Eriksson wrote:
# >
# >Somewhere between 2005.05.12.19.00.00 and 2005.05.13.18.10.00 PAM (or
# >something PAM relies on) got messed up. Installing a system with the later
# >date will prevent you from logging in, both via ssh and on the console.
# >Using ssh results in the following console output:
# >
# >sshd[530]: fatal: openpty returns device for which ttyname fails.
# >sshd[530]: error: chown 0 0 failed: No such file or directory
# >sshd[530]: error: chmod 0666 failed: No such file or directory
#
# Does backing out ttyname related changes work for you?
FWIW, the console message from syslog reads (from memory)
...root: 5 login failures on tty??...
eg two question marks instead of the correct name like "ttyv0".
Maybe that gives a clue what's wrong with the tty changes.
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
More information about the freebsd-current
mailing list