Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83 based; site homxb.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!homxb!gdsd1
From: gdsd1@homxb.UUCP (N. Nuckolls)
Newsgroups: net.micro.att,net.unix-wizards
Subject: Re:  Bizzare paranoia of /bin/login on 3b2
Message-ID: <776@homxb.UUCP>
Date: Fri, 6-Sep-85 09:28:22 EDT
Article-I.D.: homxb.776
Posted: Fri Sep  6 09:28:22 1985
Date-Received: Sat, 7-Sep-85 07:08:48 EDT
Organization: AT&T Bell Labs, Holmdel NJ
Lines: 23
Xref: watmath net.micro.att:524 net.unix-wizards:14738


>	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.

Yep, had the same experience on a 3b5 running 5.0.5 a year ago.
A non-super user would start a db server process that ignored some
signals and setpgrp() to detach from it's controlling terminal.
Everything would work great, user would log out, try to log back in
later that same day when his/her server was still running and get the
problem described above.  No problems on VAXen and 3B20S's running
5.0.5.  The quick fix was for the server to close all it's open
tty descriptors. I never looked further into the 3b5's kernel.

--
Neal Nuckolls
AT&T Bell Laboratories
HR-1A343
480 Red Hill Road
Middletown, NJ 07748
..!{ihnp4|houxa}!speedy!neal
(201) 949-9295