Path: utzoo!attcan!uunet!apctrc!gpss36!zjmw36
From: zjmw36@gpss36.trc.amoco.com (Joe M. Wade)
Newsgroups: comp.windows.x
Subject: Re: Modified xlock available?
Keywords: xlock multiuser
Message-ID: <2085@apctrc.UUCP>
Date: 3 Oct 90 16:43:44 GMT
References: <1990Sep19.103651@gila.intel.com> <1990Sep26.162710.20503@gorgo.ifi.unizh.ch>
Sender: news@trc.amoco.com
Reply-To: zjmw36@gpss36.trc.amoco.com (Joe M. Wade)
Organization: Amoco Production Company, Tulsa Research Center
Lines: 30


In article <1990Sep26.162710.20503@gorgo.ifi.unizh.ch>,
sinkwitz@gorgo.ifi.unizh.ch (Rainer Sinkwitz) writes:
|> The primary goal of xlock is to easily lock out other users from your 
|> application. 
|> 
|> xlock doesn't only do this, but is locks up the whole console
preventing other users
|> to use the X-Server and to log in.
|> 
|> So, what I'd like to see would be a xlock, that iconifies all Windows
to one icon
|> that can only be opened by password and that leaves one xterm on the
screen with
|> a login prompt. (e.g. getty). 
|> 
|> It then could do some funny things on the screen. 
|> It should also set aside the window manager ( in case one has a "new
shell" menu in it).
|> 
But couldn't somebody who's using the same server just do something like an 
xwininfo and then xkill your windows (and applications) by their ids? I know 

this would be an underhanded thing to do, but some people don't play by the 
rules.

*  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *
*  Joe M. Wade (jwade@trc.amoco.com)         (918) 660-4387    *
*  Amoco Research Center * 4502 E. 41st St. * Tulsa, OK  74102 *
*  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *