Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!agate!linus!philabs!ttidca!mb
From: mb@ttidca.TTI.COM (Michael Bloom)
Newsgroups: comp.windows.x
Subject: Re: locking X terminals
Message-ID: <20027@ttidca.TTI.COM>
Date: 25 Sep 90 08:35:06 GMT
References: <13077@june.cs.washington.edu> <1990Sep20.100335@wind.Eng.Sun.COM>
Organization: Citicorp/TTI, Santa Monica
Lines: 14

In article <1990Sep20.100335@wind.Eng.Sun.COM> Patrick Naughton writes:

>I'm putting the last few portability changes into the new xlock before
>shipping and have time for one more feature...  Do people want to be
>able to lock machines other than the one they are currently running
>on?  Before all you NCD folks jump up and say "YES.. in fact we've

Well, I think it certainly should be configurable. Also consider that if
someone really wants to lock someone else's machine, he does not need
the program "xlock". He just needs to write a few lines (:-) of code.

What I find interesting is that while the existing xlock program does
not work on NCD X terminal displays, it does in fact function properly
on Visual X terminal displays.  Would anyone care to explain why?