Commit Graph

10 Commits

Author SHA1 Message Date
Warner Losh
f1bb2cd2aa remove __P 2002-03-22 01:22:50 +00:00
David Malone
4285ad09c9 Warns cleanups:
Signal handlers are supposed to take an int as an arg.
Don't locally declare crypt or ttyname.
2001-12-03 21:01:52 +00:00
Jacques Vidrine
64ff567e0a Fix a style bug that I introduced (both sys/param.h and sys/types.h
included).

Caught by:	sheldonh@freebsd.org
1999-10-12 13:53:30 +00:00
Jacques Vidrine
65c543c764 log root unlock attempts
PR:	bin/13932
1999-10-12 13:33:48 +00:00
Peter Wemm
c3aac50f28 $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
Bruce Evans
375557fcad Don't assume that time_t is long. 1998-06-29 17:06:00 +00:00
Philippe Charnier
a4a2bc1716 Use err(3). Add usage(). 1997-07-21 12:09:34 +00:00
Warner Losh
1c8af87873 compare return value from getopt against -1 rather than EOF, per the final
posix standard on the topic.
1997-03-29 04:34:07 +00:00
Ollivier Robert
2280509ca1 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>
1996-09-14 09:00:52 +00:00
Rodney W. Grimes
9b50d90275 BSD 4.4 Lite Usr.bin Sources 1994-05-27 12:33:43 +00:00