home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sgi
- Path: sparky!uunet!europa.asd.contel.com!darwin.sura.net!sgiblab!sgigate!odin!sgihub!zola!kahua.esd.sgi.com!paquin
- From: paquin@kahua.esd.sgi.com (Tom Paquin)
- Subject: Re: Direct login failure
- Message-ID: <s60jgas@zola.esd.sgi.com>
- Sender: news@zola.esd.sgi.com (Net News)
- Organization: Silicon Graphics Inc.
- References: <96800@netnews.upenn.edu>
- Date: Tue, 10 Nov 92 04:45:19 GMT
- Lines: 21
-
- In article <96800@netnews.upenn.edu>, weemba@sagi.wistar.upenn.edu (Matthew P Wiener) writes:
- |> I have a user who cannot log in directly to one of our Iris 4Ds
- |> running 4.0.1. He tries, the screen blanks for a moment, and then
- |> he's back at the login menu. (Even with no password, he fails.)
- |> All other logins, on that machine or by that user, succeed. He
- |> has a pretty boring .login and .cshrc. Any clues?
-
- He may have a bad .sgisession or .xsession. The easy test
- is to login with "failsafe" appended; this will bring up
- a single terminal emulator and nothing else. Then you can
- try stepping through the above files. See the man pages for
- xdm etc.
-
- Eg: login: paquin failsafe
- passwd: ******
-
- --
-
- -Tom
- *****
- Opinions are mine, etc.
-