lockdisplay timeout summary
T. Pratum (pratum@u.washington.edu)
Tue, 2 Jun 1998 09:54:23 -0700 (PDT)
Surprisingly, there weren't all that many responses to my query about the
lockdisplay timeout problem, but some of us clearly are annoyed by it. I
am wondering why some of us seem to see it more than others, even though
we use the same version of xwinnmr? It was suggested by several people
that this was somehow correlated with how the lock display was closed (or
not closed) by the last user on the system; however I did try extensively
to force our most troubled instrument (dpx200) into a lock display timeout
by treating the lockdisplay window in various ways prior to logging out,
but was unable to force it to occur.
Once the lockdisplay timeout does occur, there are three things you can do
to solve it:
1. reboot the CCU (most "invasive", requires restarting xwinnmr).
2. momentarily disconnect rs232 line to LCB (pretty easy to do from my
experience).
3. kill all processes (1) that use the LCB tty (tty03 on all of our Avance
instruments- I haven't tried this one yet, but it should be pretty easy to
do).
Thanks very much to the following users who shared their experiences:
Dee-Hua Huang, Jane Strouse, Robert K. Sato, dave scott, Tim Jones,
Charles Dickinson , Art Bates, Todd Alam, Oliver Zerbe, and Frode Rise.
Tom Pratum
Dept of Chemistry
Box 351700
Univ of Washington
pratum@u.washington.edu
http://weber.u.washington.edu/~pratum