Path: utzoo!attcan!uunet!know!cs.utexas.edu!sun-barr!newstop!sun!wind.Eng.Sun.COM
From: naughton@wind.Eng.Sun.COM (Patrick Naughton)
Newsgroups: comp.windows.x
Subject: Re: locking X terminals
Message-ID: <1990Sep20.100335@wind.Eng.Sun.COM>
Date: 20 Sep 90 17:03:34 GMT
References: <13077@june.cs.washington.edu>
Sender: news@sun.Eng.Sun.COM
Reply-To: naughton@wind.Eng.Sun.COM (Patrick Naughton)
Organization: Sun Microsystems, Inc. - Mountain View, CA
Lines: 33

In article <13077@june.cs.washington.edu>,
dhubbell@june.cs.washington.edu (David Hubbell) writes:
|> xlock doesn't work on my NCD 16 and 17c X terminals.  Is this
|> because
|> 	1) I need to give some arguments to xlock.
|> 	2) The server software from NCD doesn't support locking the screen.
|> 	3) I need something other than xlock.
|> 	4) It's infeasible with X11R4.
|> 	5) You tell me.
|> 
|> 	Thanks in advance,
|> 	Dave Hubbell
--

Ok folks,

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
already hacked xlock.c to do it!" lets remember that it will be a real
pain if people are able to lock *your* screen which can only be
unlocked with *their* password.

This is a trivial change and I could controlled by the resource file,
or the command line, but I want to make sure that people *really* want
it.  (Silence is not consent... send mail if you want it.)

-Patrick
    ______________________________________________________________________
    Patrick J. Naughton				    ARPA: naughton@sun.com
    Window Systems Group			    UUCP: ...!sun!naughton
    Sun Microsystems, Inc.			    AT&T: (415) 336 - 1080