Controlling ttys, and how to get rid of them.
Chris Lewis
clewis at ecicrl.UUCP
Mon Jan 9 01:57:09 AEST 1989
In article <176 at ucms.ucms.uucp> dave at 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)
More information about the Comp.unix.questions
mailing list