Path: utzoo!utgpu!cunews!bnrgate!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: tim@sybase.com (Tim Wood)
Newsgroups: comp.sys.sun
Subject: Re: Lockscreen bypass?
Keywords: No Digest Subjects in Unmoderated Mode
Message-ID: <3230@brchh104.bnr.ca>
Date: 4 Jun 91 18:40:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sunspots, Psuedo-Unmoderated
Lines: 25
Approved: sun-spots@rice.edu
X-Original-Date:    Tue, 14 May 91 14:40:32 PDT

In article <2643@brchh104.bnr.ca> you write:
>X-Sun-Spots-Digest: Volume 10, Issue 91, message 4
>X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu
>
>I need to share a 3/60 console between two people, one working on it a few
>hours in the morning, the other in the afternoon. In between I want it to
>run lockscreen [or something to that effect] to prevent the screen
>contents to be burned into the hardware [;-)].

If that's ALL you want lockscreen for, a better arrangement is to add
a line like:
	screenblank -d 1800;	echo -n ' screenblank'
to /etc/rc.local in the "local daemons" section (for pre-4.1 OS, redirect
output of the command line to /dev/console.)  This will start a
process that turns off the screen beam after 30min. of no kbd or mouse
button activity.  If you want actual security between sessions, log
out.  Screenblank will save your hardware.
HTH,
-TW
-- 
Sybase, Inc. / 6475 Christie Ave. / Emeryville, CA / 94608	  415-596-3500
WORK:tim@sybase.com     {pacbell,pyramid,sun,{uunet,ucbvax}!mtxinu}!sybase!tim
PLAY:axolotl!tim@toad.com		       {sun,uunet}!hoptoad!axolotl!tim
Dis claim er dat claim, what's da difference?  I'm da one doin da talkin' hea.