Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site reed.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!houxm!vax135!cornell!uw-beaver!tektronix!reed!alexis
From: alexis@reed.UUCP (Alexis Dimitriadis)
Newsgroups: net.sources,net.unix
Subject: Re: lock your terminal for lunch
Message-ID: <1932@reed.UUCP>
Date: Wed, 25-Sep-85 19:34:00 EDT
Article-I.D.: reed.1932
Posted: Wed Sep 25 19:34:00 1985
Date-Received: Sat, 28-Sep-85 07:15:13 EDT
References: <132@pyuxv.UUCP> <790@mcnc.mcnc.UUCP> <3291@pur-ee.UUCP>
Reply-To: alexis@reed.UUCP (Alexis Dimitriadis)
Followup-To: net.unix
Organization: Reed College, Portland, Oregon
Lines: 23
Xref: watmath net.sources:3524 net.unix:5728

In article <3291@pur-ee.UUCP> davy@pur-ee.UUCP (Dave Curry) writes:
> 
> Here's the program I've been using for several years now to lock
> terminals... as far as I can tell, it is uninterruptible.

  To my knowledge, at least on BSD systems, there is no such thing as
an uninterruptible lock.  There are things you can do that help, but
none of the lock programs that I have seen posted do them.  If you really
want to be safe, log out when you go away.
  
  I will reply to postings from `root' if those lock programs seem secure
to you.  Much as I dislike locks (tying up a hard-to-get terminal while
the user is having his coffee strikes me as objectionable), I will not 
make those loopholes general knowledge.

PS. Followups will go to net.unix.
-- 
_______________________________________________
  As soon as I get a full time job, the opinions expressed above
will attach themselves to my employer, who will never be rid of
them again.
				alexis @ reed
    {decvax,ihnp4,ucbcad,uw-beaver}!tektronix!reed.UUCP


Brought to you by Super Global Mega Corp .com