Operating System - HP-UX
1834395 Members
1825 Online
110066 Solutions
New Discussion

Re: console login problem

 
Jun Zhang_4
Regular Advisor

console login problem

It took the root/password and showed the Copyright almost a full page until the line "You have mail", then sit there, without a command prompt. Looking at the console process, it still the getty line, without being changed to -sh. So I cannot login at the console.

Jun
Food lover
7 REPLIES 7
Massimo Bianchi
Honored Contributor

Re: console login problem

Did you try entering user and password ?

Sometimes is only a display problem. Try hitting a couple of enter...

Is the shell allright ? MUST be /sbin/sh

Is there any nfs_mount in the PATH? this can cause very long login times..

Is there anything in the .profile that can consume time ?

Is this only from console or also from telnet logins ?

Massimo


DGH_2
Valued Contributor

Re: console login problem

Hi
what did you changed on the systemrecently to reboot it?

did you try to telnet the system?

GDH
Jun Zhang_4
Regular Advisor

Re: console login problem

root does use /sbin/sh, home dir is /.
The problem occurs only at the console, telnet sessions are fine.
I did nfs mounted a cdrom drive from a linux machine. The drive was mounted and functional when console login was attempted.
No related message in syslog.log.


Jun
Food lover
Jun Zhang_4
Regular Advisor

Re: console login problem

I repowered the dumb terminal, and the root pound sign is already there, all functional. If I relogin, the whole procedure is repeated. So there is still a (strange) problem.

Jun
Food lover
Mark Greene_1
Honored Contributor

Re: console login problem

What's in /etc/securetty and /etc/gettydefs?

mark
the future will be a lot like now, only later
Massimo Bianchi
Honored Contributor

Re: console login problem

If you can,
try renaming the .profile and login again...

Massimo
doug hosking
Esteemed Contributor

Re: console login problem

You power cycled the terminal and things recovered? That sounds like maybe your login session is sending out control codes that lock the keyboard. Check the bottom of the terminal and see if there's anything like 'kbd locked' or 'keyboard locked' messages. Sometimes that can happen when your .login/.profile is querying for terminal type.