xlock for SUNS and Xterminals
2007-12-25 8:20:00
>I have been trying to locate a version of xlock that works on X terminals and
>SUNs. I called our X terminal vendor, and he said the xlock from Openwindow
>3.0 should work. I have the following version:
>
>% what xlock | grep xlock
>xlock:
> xlock.c 23.21 91/09/14 XLOCK
>
>When it is run on an X terminal or PC running an X server, you get a message
>something like:
>
>% xlock -remote
>X Error: BadAccess
> Request Major code 109 ()
> Error Serial #93
> Current Serial #96
>% xhost
>access control disabled (any host is allowed)
>earth
>mars
>% env | grep DIS
>DISPLAY=mars:0.0
>
>I am running SUN O/S 4.1.1 and 4.1.3 with vanilla X11R4 and Openwindows 2.0
>and 3.0. We have various SUNs and X terminals / servers.
>
>My primary problem is that a previous employee found source to X locking
>programs called xlock and xidlelock and "customized" them as part of an
>"application". This application is supposed to lock the screen after the
>keyboard and mouse are idle for 10 minutes. It has a bug in it somewhere and
>does not work on X terminals. The life program of xlock will start up at a
>random time, lock the screen and not allow sufficient time to type a
>password. In addition, if the user gets in a password, the lock starts again.
>My user cannot use his new X terminals with the dreaded application and is
>not >happy ! (It works fine on SUNS, as does the Openwindows 3.0 xlock).
>
>Questions:
>1) what is wrong with the xlock version from Openwindows 3.0 above, since it
>is supposed to support the -remote option ?
>
>2) where can I get current versions of the source to xlock and xidlelock that
>work on SUNs, X terminals, and PC X Servers.
>
>
>Anthony
Answers:
1) The xlock from openwindow 3.0 works with everywhere (PC's, SUNS,
Xterminals) with the options: xlock -remote -allowaccess
2) xlock can ftped from various locations. I used the one from comp.sources.x
volume 10 archives.
Thanks to all
Anthony
Comments
Got something to say?
You must be logged in to post a comment.
