[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20010423: solaris 8, mike schmidt ?



>From: alan anderson <address@hidden>
>Organization: St. Cloud State
>Keywords: 200104231612.f3NGCtL05653 Solaris 8 SPARC lock

Alan,

I just chatted with Mike about your problem.  He did get your original
email and the resend this morning.  Unfortunately, he has not yet had
time to consider your situation and compose a reply.  I believe that
he will be attempting to free up some time either later today or tomorrow
to look at your problem.

Tom Yoksas

>Last week I sent a message to support about a problem we are having 
>with terminals locking up .   Maybe it missed you, so have repeated it
>below.  Let me know if you saw it, even if you don't have an answer.
>I do have a few more details, but will wait for your confirmation.
>
>Thanks
>Alan 
>
>
>Message of  4/19
>My problem is a situation where after a user leaves a terminal,
>and with no problems to that point.  After a time the screen 
>reverts to dark.  When a key is touched, a small window appears
>with the message:
>                  Display locked by user  'username'
>                  Enter passwork to unlock.
>
>                  Password  _____________
>
>All of this is normal and this locking is as described in 
>the documentation for Solaris.
>
>We have two terminals which cannot be unlocked after the above 
>described sequence.  Upon typing the correct password, the only return is a
>beep.
>This locking does not seem to occur if the login user is root, but it does
>occur for all other users.  
>
>I have been able to get in the terminal using telnet from another 
>machine.  Log in, su to root and shutdown/reboot the machine.
>
>Upon a reboot,  the normal login screen appears, so users can start 
>fresh.  MCIDAS runs ok and all else appears ok,  no hangs or error 
>messages.  If the terminal is left idle for a few minutes, the locked 
>screen message reappears and the problem is back.  
>
>I have looked in the desktop control items to find and reset things 
>like power management (disable) and screen display lock (disable) 
>but this problem keeps coming back.  Also looked in the documentation
>on things like display locked, suspend ... but find nothing that 
>helps me.
>
>There is no history of other strange problems on either terminal.  This 
>problem appeared last week, after a glitch with MCIDAS which locked
>up the machine.  After a hard boot, everything came back, and MCIDAS 
>seemed to run ok, but after leaving the terminal idle, this locked 
>behavior began. 
>
>I don't want to resort to reinstalling the OS, but am stuck.
>
>Any suggestions ?    There are two machines with same symptoms.
>                     One is  IP 199.17.31.12  pass is mikes79
>
>Thanks
>
>Alan