summaryrefslogtreecommitdiffstats
path: root/usr.bin/lockf
Commit message (Collapse)AuthorAgeFilesLines
* Add history.obrien2000-12-101-0/+4
|
* $Id$ -> $FreeBSD$peter1999-08-283-3/+3
|
* Add a "-k" option, to specify that the lock file should be keptjdp1998-07-082-13/+27
| | | | | | rather than removed. Submitted by: Nick Barnes <Nick.Barnes@pobox.com>
* .Sh AUTHOR -> .Sh AUTHORS. Use .An/.Aq.charnier1998-03-231-4/+3
|
* lockf: usage : lockf -> usage: lockf by using fprintf instead of errx.charnier1997-07-221-2/+4
|
* compare return value from getopt against -1 rather than EOF, per the finalimp1997-03-291-2/+2
| | | | posix standard on the topic.
* Revert $FreeBSD$ to $Id$peter1997-02-223-3/+3
|
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-143-3/+3
| | | | | | | | This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long. Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
* On failure, return various exit codes from <sysexits.h>. In particular,jdp1997-01-092-17/+34
| | | | | | | | | | return EX_TEMPFAIL if the file was already locked. This makes it easier to distinguish between lock collisions and failures within the command being executed. Also, don't complain if the unlink() fails in the cleanup handler. It doesn't matter anyway, and it obscured the exit status returned from the command that was executed.
* Initial import of the lockf utility. It executes an arbitrary commandjdp1997-01-083-0/+314
while holding an exclusive lock on a file.
OpenPOWER on IntegriCloud