Original Question:
^^^^^^^^^^^^^^^^^^
The console seems to be not unlockable (it stays locked no matter what I do
with dxdevices). This is for an ordinary user login, not for root (which I
haven't tried as the console is some way from my office.)
Searching the archives on this one reveals that:
>>
>> I can't figure out what is happening, and don't know where i could
>>find information on the name of the terminal which is disabled.
>
> finally, I understood that devices could be unlocked with dxdevices,
>with modify devices, by clicking on a device and then on the edit button,
>but *not* double-clicking on the device, which brings up a new window
>from which the operation is impossible. You'll have to unlock a device
>blindly, though, because there is no way to say if it is locked or not.
I've tried unlocking the console via dxdevices as directed, but I haven't
tried rebuilding the db with edauth.
Anyone got ideas on this one? I'm using 4.0F and the patches that shipped
with it. Is it really a bug? and if so, is it fixed in a patch kit?
Summary:
^^^^^^^^
The "console" device appears not to have been the problem, even though the
user was attempting the login directly from the system console. The device
which was locked was :0.0 - the X alias for the console, which is listed
as a separate device from the official "console".
dxdevices was completely non-functional in fixing the problem, nor does it
have any way to tell you whether or not the device is locked. dxdevices
appears to be early "alpha" quality - it has very limited functionality,
and is missing the essentials. On the other hand, it didn't crash.
Although the man pages do not indicate what the values should be for the
variables mentioned in the man page for ttys(4); what I wound up doing was
to use edauth and actually remove the variable t_lock from the locked
device. I also lowered the count on t_failures from 29 (!!) to 0, however,
this had no effect until I removed the t_lock variable.
This stuff is very poorly documented.
Details of the two answers I got:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
X-Mailer: XFMail 1.2 [p0] on OSF1
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <4.2.0.58.19991115175720.00bf37b0_at_137.197.214.37>
Date: Tue, 16 Nov 1999 08:46:14 +0100 (MET)
Organization: CUST, Universite Blaise Pascal, Clermont-Ferrand, FRANCE
From: mc.vialatte_at_custsv.univ-bpclermont.fr
To: Chad Price <cprice_at_molbio.unmc.edu>
Subject: RE: terminal disabled
X-UIDL: b44312196db048a22913593ef349c112
Le 16-Nov-99 Chad Price a ecrit :
> The console seems to be not unlockable (it stays locked no matter what
I do
> with dxdevices).
Have you try edauth(8) in place of dxdevices ?
edauth -d t console
then edit the console entry as explained in ttys(4).
You may change all or some of t_failures, t_maxtries, t_lock and
t_unlock fields.
_
>Sender: root_at_Uprava.ev.co.yu
>Date: Tue, 16 Nov 1999 08:37:56 +0100
>From: Nikola Milutinovic <Nikola.Milutinovic_at_ev.co.yu>
>Organization: EPS Elektrovojvodina
>X-Mailer: Mozilla 4.7 [en] (X11; I; OSF1 V4.0 alpha)
>X-Accept-Language: en
>To: Chad Price <cprice_at_molbio.unmc.edu>
>Subject: Re: terminal disabled
>
>Chad Price wrote:
> >
> > The console seems to be not unlockable (it stays locked no matter what I do
> > with dxdevices). This is for an ordinary user login, not for root (which I
> > haven't tried as the console is some way from my office.)
> >
> > Searching the archives on this one reveals that:
> >
> > >>
> > >> I can't figure out what is happening, and don't know where i
> could
> > >>find information on the name of the terminal which is disabled.
> > >
> > > finally, I understood that devices could be unlocked with
> dxdevices,
> > >with modify devices, by clicking on a device and then on the edit button,
> > >but *not* double-clicking on the device, which brings up a new window
> > >from which the operation is impossible. You'll have to unlock a device
> > >blindly, though, because there is no way to say if it is locked or not.
> >
> > I've tried unlocking the console via dxdevices as directed, but I haven't
> > tried rebuilding the db with edauth.
> >
> > Anyone got ideas on this one? I'm using 4.0F and the patches that shipped
> > with it. Is it really a bug? and if so, is it fixed in a patch kit?
>
>When you say "console", what are you referring to? "/dev/console" or X login?
>
>Any login capable device is described in ttys.db, try "edauth -g -dt >
>report.txt" and look for "failures". If the num is greater than 10, it is
>locked
>and dxdevices is dumb not to notice it. Frankly, dxaccounts and dxaudit work,
>dxdevices, I'm not sure of. I strongly recommend familiarizing yourself with
>"edauth", "authck" and others.
Chad Price
Systems Manager, Genetic Sequence Analysis Facility
University of Nebraska Medical Center
986495 Nebraska Medical Center
Omaha, NE 68506-6495
cprice_at_molbio.unmc.edu
(402) 559-9527
(402) 559-4077 (FAX)
Received on Wed Nov 24 1999 - 22:42:36 NZDT