Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 from ihnp4 4.3bsd-beta 6/6/85; site chinet.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!chinet!djc
From: djc@chinet.UUCP (David J. Carpenter)
Newsgroups: net.micro.att,net.unix-wizards
Subject: Bizzare paranoia of /bin/login on 3b2
Message-ID: <174@chinet.UUCP>
Date: Thu, 5-Sep-85 16:29:35 EDT
Article-I.D.: chinet.174
Posted: Thu Sep  5 16:29:35 1985
Date-Received: Fri, 6-Sep-85 05:44:59 EDT
Reply-To: djc@chinet.UUCP (David J. Carpenter)
Organization: chinet, Public Access UN*X, Chicago IL
Lines: 24
Xref: watmath net.micro.att:521 net.unix-wizards:14725

I have experienced a bizzare problem with logging in on the console
on our 3b2.  Here's what would happen:  Unix: would send  login: , I
would reply, then Unix would send Login incorrect immediately without
asking for a password.  I immediately feared that something happened
to /etc/passwd.  But I went to other terminals and was able to login
without any problem.  Then I found that the console would allow me to
login as guest, which didn't have a password, but from guest, su
replied with Sorry without asking for a password.  When on as guest,
the ps command reported that my login -sh was not associated with
a terminal.
	The only major change I had recently made of significance was
to change a line in /etc/inittab from a uugetty to a shell script
that did a few things, then exec'd uugetty.  Doing a ps from another
terminal revealed that this shell script was associated with console.
	So apparently, for some reason INIT made the shell script in
console group, and when login started up on the console it didn't like
having another process associated with console and got suspicious.
Switching back the /etc/inittab line solved the problem.
	Anybody know anything about this?   Thanks...

-- 
					...!ihnp4!chinet!djc
					David Carpenter
					(312) 545-8076