Re: R4000 Indy login problems
"Stephen M. Rumble" <[email protected]> Sat, 7 Mar 2009 07:38:40 -0800
| Newsgroups | gmane.os.netbsd.ports.sgimips |
|---|---|
| Message-ID | <[email protected]> |
On Mar 7, 2009, at 4:34 AM, Frank Wille wrote: > Hi, > > with all the recent kernels I have a strange problem with getty and/ > or login. I think that I ran into this a month or two ago, after the 64-bit time_t changes. I believe it had something to do with broken backwards compatibility. jmmv@ figured it out. I'm CC'ing him in case it was never fixed. Ah, here it is: http://julipedia.blogspot.com/2009/01/pwdmkdb-and-new-timet.html Steve > > My user shell is not launched (but there is no core dump), and the > getty > restarts. In this example I'm logging in with the correct password: > > ---8<--- > login: root > password: > Mar 7 11:22:23 indy login: ROOT LOGIN (root) ON console > > NetBSD/sgimips (indy.owl.de) (console) > > login: > ---8<--- > > The authog receives an entry about a root-login, but getty just > restarts... > > When using a wrong password, it looks like this: > ---8<--- > login: root > password: > Login incorrect or refused on this terminal. > ---8<--- > > Similar problem when logging in via ssh from a different system: > > ---8<--- > frank@compaq ssh indy > Password: > Connection to indy closed by remote host. > Connection to indy closed. > ---8<--- > > The password is accepted, but I'm immediately losing connection. > I also tried it with a normal user and a different shell (tcsh > instead of > sh). No difference. > > Maybe another side effect of the R4000 bugs? But it worked with older > kernels. > > Anybody observed the same? How to debug that? In getty or login? > > > -- > _ Frank Wille ([email protected]) > _ // http://sun.hasenbraten.de/~frank/ > \X/ Phx @ #AmigaGer >