Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!mcnc!thorin!unc!certain
From: certain@unc.cs.unc.edu (Andrew Certain)
Newsgroups: comp.unix.aux
Subject: Re: can't login from console
Summary: Fix for logins from console refused?
Keywords: console login fix
Message-ID: <8651@thorin.cs.unc.edu>
Date: 27 Jun 89 16:34:34 GMT
References: <1618@cunixc.cc.columbia.edu> <8595@pyr.gatech.EDU>
Sender: news@thorin.cs.unc.edu
Reply-To: certain@unc.cs.unc.edu (Andrew Certain)
Distribution: usa
Organization: University Of North Carolina, Chapel Hill
Lines: 29

In article <1618@cunixc.cc.columbia.edu> marg@cunixc.cc.columbia.edu (Margarita
Suarez) writes:
>hi, i just inherited a mac II/X with an 80SC with A/UX.  i've not been
>able to boot multi-user from the console -- what happens when i type
>"telinit 2" is an infinite loop of "login:" immediately followed by
>"Login incorrect" (didn't ask for password).

In article <8595@pyr.gatech.EDU> glenn@aspen.ga.UUCP (Glenn Souther) writes:
>I have seen a similar problem here. However, in our case the machine stays up
>for a while, and later when an account name is entered at login: the machine
>immediately responds with "login incorrect" without asking for a password.

I have also experienced this problem.  I haven't yet determined what the cause
is, but if you have an account that doesn't require a password, you can log
in with that.  For other reasons, we had an account set up that would, if you
were at the console and typed "reboot" at the login prompt, reboot the
machine.  Since this syncs the disks, it isn't as harsh as hitting the reboot
switch.  One day, when this problem arose,  I typed reboot at the login prompt
to reboot the machine, but instead of rebooting the machine, it cleared up the
problem.....  Believe it, or not.

The reboot login is very simple... The .login has logout in it, and .logout
says if tty = console then sync;sync;sync;reboot (written more precisely in
C-Shell script).  I don't claim that this will work everytime or even at all,
and I don't claim that it won't actually reboot your machine.  Proceed at your
own risk.  I'm just telling you my experience.

Andrew Certain
certain@cs.unc.edu