From owner-cvs-usrbin  Sat Sep 14 02:01:18 1996
Return-Path: owner-cvs-usrbin
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id CAA24964
          for cvs-usrbin-outgoing; Sat, 14 Sep 1996 02:01:18 -0700 (PDT)
Received: (from roberto@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id CAA24938;
          Sat, 14 Sep 1996 02:01:01 -0700 (PDT)
Date: Sat, 14 Sep 1996 02:01:01 -0700 (PDT)
From: Ollivier Robert <roberto>
Message-Id: <199609140901.CAA24938@freefall.freebsd.org>
To: CVS-committers, cvs-all, cvs-usrbin
Subject: cvs commit:  src/usr.bin/lock lock.1 lock.c
Sender: owner-cvs-usrbin@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

roberto     96/09/14 02:01:00

  Modified:    usr.bin/lock  lock.1 lock.c
  Log:
  Closes PR bin/1567
  
  /usr/bin/lock can be used to lock a terminal much like xlock does
  for your X-windows session.  Problem is, /usr/bin/lock cannot lock
  your terminal indefinately.  Rather you must specify a timeout
  value, after which, your terminal is unlocked and become unsecured.
  
  I have added a ``-n'' no timeout option to /usr/bin/lock
  Currently the only way to get this functionality is to use a huge
  timeout value and hope it is long enought (in time).  This method
  also requires you to know the maxium number of minutes you are
  allowed to specify.
  
  Submitted by:	David E. O'Brien <obrien@Nuxi.cs.ucdavis.edu>
  
  Revision  Changes    Path
  1.2       +3 -0      src/usr.bin/lock/lock.1
  1.2       +29 -9     src/usr.bin/lock/lock.c