Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 14 May 2005 14:22:19 +0200
From:      Jens Schweikhardt <schweikh@schweikhardt.net>
To:        Tai-hwa Liang <avatar@mmlab.cse.yzu.edu.tw>
Cc:        Daniel Eriksson <daniel_k_eriksson@telia.com>
Subject:   Re: PAM breakage
Message-ID:  <20050514122219.GB1621@schweikhardt.net>
In-Reply-To: <0505141523488.66026@www.mmlab.cse.yzu.edu.tw>
References:  <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAAcgWdwjr8+UCYYaYPJq4uSgEAAAAA@telia.com> <0505141523488.66026@www.mmlab.cse.yzu.edu.tw>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
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)



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20050514122219.GB1621>