summaryrefslogtreecommitdiffstats
path: root/usr.bin/lock
Commit message (Collapse)AuthorAgeFilesLines
* Remove useless `BINOWN=root' now that it is the default.obrien1998-09-191-1/+0
|
* Don't assume that time_t is long.bde1998-06-291-2/+4
|
* Use err(3). Add usage().charnier1997-07-211-28/+31
|
* compare return value from getopt against -1 rather than EOF, per the finalimp1997-03-291-1/+1
| | | | posix standard on the topic.
* Closes PR bin/1567roberto1996-09-142-9/+32
| | | | | | | | | | | | | | | /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>
* Add dependencies on libraries to DPADD. Someday this should be donebde1994-08-281-0/+1
| | | | | | automagically. -lfoo has to be right to work, but ${LIBFO0} is too easy to forget or misspell; nothing checks it and it should be different for shared libraries.
* LDADD= -lcryptcsgr1994-08-201-0/+1
| | | | Submitted by: Geoff
* BSD 4.4 Lite Usr.bin Sourcesrgrimes1994-05-273-0/+298
OpenPOWER on IntegriCloud