[18287] in Athena Bugs
sun4 8.4.12: xlock
daemon@ATHENA.MIT.EDU (David Z. Maze)
Sun Sep 17 15:27:29 2000
Message-Id: <200009171927.PAA02701@x15-cruise-basselope.mit.edu>
To: bugs@MIT.EDU
Date: Sun, 17 Sep 2000 15:27:24 -0400
From: "David Z. Maze" <dmaze@MIT.EDU>
System name: x15-cruise-basselope.mit.edu
Type and version: Ultra-5_10 8.4.12 (with mkserv)
Display type: afb
Shell: /bin/sh (/afs/sipb/project/sipb/bin/zsh?)
Window manager: ssh-agent fvwm2
What were you trying to do?
Help a user who came into the SIPB office who had locked her
workstation with 'xlock.real', and couldn't unlock it because
xss had come up and the two screensavers deadlocked on
keyboard input.
What's wrong:
On public workstations, /usr/athena/bin/xlock prints a message
saying,
If you really wish to run xlock, run it as 'xlock.real' instead.
But if you do so, others may legitimately reboot the machine at
any time to log you out.
This message leads users to naively and blindly run 'xlock.real',
since it's general knowledge that you use 'xlock' to lock the X
display on Unixish workstations.
What should have happened:
The message should tell people to not run xlock.real, since
they most likely won't be able to unlock the screen. xlock.real
should be renamed to something else, like 'xlock.yes-i-mean-it'.
The xlock wrapper should advise people to run 'xss-command -lock'.
Please describe any relevant documentation references:
'()
