summaryrefslogtreecommitdiffstats
path: root/usr.bin/lockf/lockf.1
Commit message (Collapse)AuthorAgeFilesLines
* Lockf was exiting with status 1 if the command did not exit normally.dwmalone2008-08-211-0/+5
| | | | | | | This is easy to confuse with the actual exit status of the program. Instead exit with EX_SOFTWARE if the command doesn't exit normally. MFC after: 1 month
* Also fix a "blank line" issue that sneaked in from rev. 1.19.ru2007-10-311-1/+1
| | | | Submitted by: John Hein
* Remove newly acquired hard sentence breaks.ru2007-10-301-2/+4
|
* Revision 1.12 of lockf.c fixed a "thundering herd" scenario when thecsjp2007-10-121-1/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | lock experienced contention a number of processes would race to acquire lock when it was released. This problem resulted in a lot of CPU load as well as locks being picked up out of order. Unfortunately, a regression snuck in which allowed multiple threads to pickup the same lock when -k was not used. This could occur when multiple processes open a file descriptor to inode X (one process will be blocked) and the file is unlinked on unlock (thereby removing the directory entry allow another process to create a new directory entry for the same file name and lock it). This changes restores the old algorithm of: wait for the lock, then acquire lock when we want to unlink the file on exit (specifically when -k is not used) and keeps the new algorithm for when -k is used, which yields fairness and improved performance. Also, update the man page to inform users that if lockf(1) is being used to facilitate concurrency between a number of processes, it is recommended that -k be used to reduce CPU load and yeld fairness with regard to lock ordering. Collaborated with: jdp PR: bin/114341 PR: bin/116543 PR: bin/111101 MFC after: 1 week
* Markup cosmetics.ru2006-12-201-4/+6
|
* Fix all the spelling mistakes I could find in the man pages for wordskeramida2005-07-311-1/+1
| | | | | | | | that have at least 3 characters. MFC after: 1 week Thanks to: Music band ``Chingon'' for keeping me company while searching for these.
* Markup and wording fixes.ru2005-06-141-1/+3
| | | | Approved by: re (blanket)
* Document a couple of gotchas.eivind2005-05-261-1/+7
|
* Added the EXIT STATUS section where appropriate.ru2005-01-171-1/+1
|
* Mechanically kill hard sentence breaks.ru2004-07-021-2/+4
|
* Use `The .Nm utility'charnier2002-04-201-1/+4
|
* mdoc(7) police: s/BSD/.Bx/ where appropriate.ru2001-08-141-1/+3
|
* Remove whitespace at EOL.dd2001-07-151-1/+1
|
* mdoc(7) police: removed HISTORY info from the .Os call.ru2001-07-101-1/+1
|
* Add history.obrien2000-12-101-0/+4
|
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* Add a "-k" option, to specify that the lock file should be keptjdp1998-07-081-7/+12
| | | | | | rather than removed. Submitted by: Nick Barnes <Nick.Barnes@pobox.com>
* .Sh AUTHOR -> .Sh AUTHORS. Use .An/.Aq.charnier1998-03-231-4/+3
|
* Revert $FreeBSD$ to $Id$peter1997-02-221-1/+1
|
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-141-1/+1
| | | | | | | | 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-091-4/+21
| | | | | | | | | | 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-081-0/+95
while holding an exclusive lock on a file.
OpenPOWER on IntegriCloud