Xref: utzoo comp.unix.wizards:13955 comp.unix.questions:10989
Path: utzoo!attcan!lsuc!ecicrl!clewis
From: clewis@ecicrl.UUCP (Chris Lewis)
Newsgroups: comp.unix.wizards,comp.unix.questions
Subject: Re: Controlling ttys, and how to get rid of them.
Keywords: System V, login, tty
Message-ID: <184@ecicrl.UUCP>
Date: 8 Jan 89 15:57:09 GMT
References: <176@ucms.ucms.uucp>
Reply-To: clewis@ecicrl.UUCP (Chris Lewis)
Organization: Elegant Communications Inc. (CRL Division)
Lines: 29

In article <176@ucms.ucms.uucp> dave@ucms.UUCP (Dave Settle) writes:

>What happens is that in some circumstances, I can only login using an account
>without a password. If I try to login as a user who has a password, I get:

>Machine XYZ .... etc
>login: dave
>Login incorrect
>login:

>This affects every user who has a password, but only affects the one terminal -
>I can login on other terminals fine (it asks for my password as per usual).

I've seen this occur a couple of times on 386/ix - to confirm, after 
successfully logging in on the port that's acting wierd, do this:

	echo hello > /dev/tty

Ours comes back with "can't open".  Killing everything in sight on that
line usually helps.  Used to get it with a serial device driver we hadn't
got working w.r.t. setting process groups.

[The reason why this relates is that login can't stty -echo when ttyname
or isatty fails which they will do if /dev/tty won't open]
-- 
Chris Lewis, Markham, Ontario, Canada
{uunet!attcan,utgpu,yunexus,utzoo}!lsuc!ecicrl!clewis
Ferret Mailing list: ...!lsuc!gate!eci386!ferret-request
(or lsuc!gate!eci386!clewis or lsuc!clewis)