Path: utzoo!utgpu!cunews!bnrgate!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: uaisun4!mrl@uunet.uu.net (Mark R. Ludwig)
Newsgroups: comp.sys.sun
Subject: Re: Lockscreen bypass?
Keywords: Miscellaneous
Message-ID: <2780@brchh104.bnr.ca>
Date: 9 May 91 23:05:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 15
Approved: Sun-Spots@rice.edu
X-Original-Date: Mon, 29 Apr 91 09:00:53 PDT
X-Refs:  Original: v10n91
X-Sun-Spots-Digest: Volume 10, Issue 99, message 9
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

In article <2643@brchh104.bnr.ca>, cnix!klaus@uunet (klaus u schallhorn) writes:
>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 [;-)].

Perhaps you want to run ``screenblank'' instead.  It watches the keyboard
and mouse for input, and the console for output, and "turns off the
display" when idle for 10 minutes (by default).  I start it in
``rc.local'' so it's always protecting the screen.  The one annoying
feature of it which I've found is that when no one is logged in, you have
to press an echoing key before the display resumes.  (Entering your userid
to start your login works, of course.)  When you're logged in, you can
press *any* key (such as Shift) and the display will resume.