| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
of ioctl TIOCGETP/TIOCSETP.
|
|
|
|
|
|
|
|
|
| |
Add some constness to avoid some warnings.
Remove use register keyword.
Deal with missing/unneeded extern/prototypes.
Some minor type changes/casts to avoid warnings.
Reviewed by: md5
|
|
|
|
|
| |
terminal is locked. This permits the user to easily lock the entire
console from a single terminal.
|
|
|
|
| |
doesn't (and shouldn't) work.
|
|
|
|
|
|
|
|
| |
don't use spaces at the beginning of a line where tabs are normally
used (the worst thing was that half of this file was right (tabs) and
half was wrong (spaces), making for painful reading).
Reviewed by: /sbin/md5, diff -b
|
| |
|
| |
|
|
|
|
|
| |
Signal handlers are supposed to take an int as an arg.
Don't locally declare crypt or ttyname.
|
|
|
|
|
|
| |
included).
Caught by: sheldonh@freebsd.org
|
|
|
|
| |
PR: bin/13932
|
| |
|
| |
|
| |
|
|
|
|
| |
posix standard on the topic.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
/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>
|
|
|