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?
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 Tue Nov 16 1999 - 00:02:00 NZDT