Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Don't assume that time_t is long. | bde | 1998-06-29 | 1 | -2/+4 |
| | |||||
* | Use err(3). Add usage(). | charnier | 1997-07-21 | 1 | -28/+31 |
| | |||||
* | compare return value from getopt against -1 rather than EOF, per the final | imp | 1997-03-29 | 1 | -1/+1 |
| | | | | posix standard on the topic. | ||||
* | Closes PR bin/1567 | roberto | 1996-09-14 | 2 | -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 done | bde | 1994-08-28 | 1 | -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= -lcrypt | csgr | 1994-08-20 | 1 | -0/+1 |
| | | | | Submitted by: Geoff | ||||
* | BSD 4.4 Lite Usr.bin Sources | rgrimes | 1994-05-27 | 3 | -0/+298 |