clercqm@nijmeg (Marien de Clercq) (02/18/91)
Lately I have problems with a particular login on an Intergraph IS6000 machine running CLIX (Intergraph's Unix) R3.1 version Vc.4.0.9. The problem is that when I login in as one particular user, after giving in the password the machine 'hangs'. It does not react anymore to the keyboard and the only way to get out of this is to kill the window (or the session on the terminal server). The strange thing about this is that login in as another user who uses the same home directory and '.profile' as the one that gets stuck, works fine. If I 'su' to the user who gets stuck with the '-' option, the login hangs after the password, just as when login in from the login prompt. But if I do it without the '-' option, it works fine. When I then execute the '.profile', that also works fine (so does it for the other user that uses the same '.profile'). I also tried if removing and adding the user back to the system would help, but the same thing kept happening. So it seems to me that something strange must happen after the acceptation of the password and before the execution of '.profile' (and probably before the execution of '/etc/profile'. And that only happens for this particular user, no other account on this machine has any such problems. And the problems with this one just started to happen from one day on another ! Can anyone help me, because now I have to login as another user, 'su' to the one with the problems, 'cd' to it's home directory and execute the '.profile' everytime before being able to work as the user with the login problem. And that's becoming a bore. Marien de Clercq Intergraph European Manufacturing - bv. Nijmegen - The Netherlands mail: ..!uunet!ingr!nijmeg!m_clercq
weimer@garden.kodak.COM (Gary Weimer (588-0953)) (02/19/91)
In article <1991Feb18.112320.25917@nijmeg> you write: |> |> Lately I have problems with a particular login on an Intergraph IS6000 |> machine running CLIX (Intergraph's Unix) R3.1 version Vc.4.0.9. Some things to check: 1) the login shell for the problem user id. This is in /etc/passwd on many systems. Make sure the entry for the problem user id has the correct number of fields (separated by ':'). 2) Does another user id have the same login id number as another user id? 3) Some systems have problems with long user id's. Does the problem user id have more than 8 characters? (Note: this doesn't seem likely to be the problem.) weimer@ssd.kodak.com ( Gary Weimer )
jerry@ora.com (Jerry Peek) (02/19/91)
In article <1991Feb18.112320.25917@nijmeg> clercqm@nijmeg (Marien de Clercq) writes: > The problem is that when I login in as one particular user, after giving in > the password the machine 'hangs'. It does not react anymore to the keyboard > and the only way to get out of this is to kill the window (or the session on > the terminal server). Here are a couple of ways I've traced login problems before. These both assume that your shell gets started and reads the .profile. Putting this line at the top of the .profile will tell you whether the .profile is being read at all and where it hangs: set -xv you'll see each line read from the .profile and the commands executed on the screen. If you don't see anything, then the shell probably didn't read the .profile. The reason might also be that you just aren't getting any output to the terminal, for some very weird reason. Then the "set -xv" wouldn't help you. In that case, try adding this line to the start of the .profile: exec > /tmp/sh.out.$$ 2>&1 If the shell starts reading the .profile, that'll make a file in /tmp called sh.out.nnnnn with output from the commands and the shell's "set -xv". --Jerry Peek, O'Reilly & Associates, Inc. jerry@ora.com
tensmekl@infonode.ingr.com (Kermit Tensmeyer) (02/20/91)
In article <1991Feb18.112320.25917@nijmeg> clercqm@nijmeg (Marien de Clercq) writes: > >Lately I have problems with a particular login on an Intergraph IS6000 >machine running CLIX (Intergraph's Unix) R3.1 version Vc.4.0.9. > >The problem is that when I login in as one particular user, after giving in >the password the machine 'hangs'. It does not react anymore to the keyboard >and the only way to get out of this is to kill the window (or the session on >the terminal server). >The strange thing about this is that login in as another user who uses the same >home directory and '.profile' as the one that gets stuck, works fine. >If I 'su' to the user who gets stuck with the '-' option, the login hangs >after the password, just as when login in from the login prompt. >But if I do it without the '-' option, it works fine. When I then execute the >'.profile', that also works fine (so does it for the other user that uses the >same '.profile'). > For the project, that I'm working on now, we sometimes used several users in the same home directory. We would get problems much the same if the user didn't have permission to access some of the files. Check for instance the .sh_history file or the .env files. Also as others have stated, check the values for owner and group in the /etc/passwd. try su -le <new uid> as well. > >Can anyone help me, because now I have to login as another user, 'su' >to the one with the problems, 'cd' to it's home directory and execute the >'.profile' everytime before being able to work as the user with the login >problem. And that's becoming a bore. > > >Marien de Clercq > >Intergraph European Manufacturing - bv. >Nijmegen - The Netherlands > >mail: ..!uunet!ingr!nijmeg!m_clercq -- Kermit Tensmeyer | Intergraph Corporation UUCP: ...uunet!ingr!tensmekl | One Madison Industrial Park INTERNET: tensmekl@ingr.com | Mail Stop LR23A2 AT&T: (205)730-8127 | Huntsville, AL 35807-4201
pww@bnr.ca (Peter Whittaker) (02/20/91)
In article <1991Feb18.112320.25917@nijmeg> clercqm@nijmeg (Marien de Clercq) writes: > The problem is that when I login in as one particular user, after giving in > the password the machine 'hangs'. It does not react anymore to the keyboard > and the only way to get out of this is to kill the window (or the session on > the terminal server). One possibility: do you have any NFS mounts? If that particular ID is attempting to set its path variable to a set of directories that includes an NFS mounted disk that is not available, then you will not be able to proceed past the 'set path=dfjkf' part of your .cshrc or .login.... If this is the problem, either remove the annoying element from the path, or mount the particular file system soft (hard is the default) and specify a bound on retry. RTFM for NFS, pating close attention to intr, soft, retry. -- Peter Whittaker [~~~~~~~~~~~~~~~~~~~~~~~~~~] Open Systems Integration pww@bnr.ca [ ] Bell Northern Research Ph: +1 613 765 2064 [ ] P.O. Box 3511, Station C FAX:+1 613 763 3283 [__________________________] Ottawa, Ontario, K1Y 4H7