runlock(1) [debian man page]
RUNLOCK(1) General Commands Manual RUNLOCK(1) NAME
runlock - prevent concurrent execution of a process SYNOPSYS
runlock [ -h ] runlock [ -d ] [ -f pathname ] [ -t timeout ] command [ args ] DESCRIPTION
runlock tries to hold an exclusive lock while it executes a command. Subsequent execution of runlock with the same lock, while that lock is held, will cause the new instance of runlock to terminate with a faliure exit code. Otherwise, the exit code of the subprocess is returned. USAGE
-d Debug mode; send log messages to standard error as well as to the system log. -f pathname Specifies the pathname of the file to use as a lock file. The default is to create a lock file in /tmp/cronutils-$USER with the name of the command, and suffix ".pid". -t timeout Specifies the duration, in seconds, for runlock to wait before giving up on trying to acquire the lock. The default is 5 seconds. -h Prints some basic help. BUGS
Sending SIGALRM to runlock before the timer has expired will cause the subprocess to be killed. SEE ALSO
runalarm(1), runstat(1) AUTHOR
runlock was written by Jamie Wilkinson <jaq@google.com>. COPYRIGHT
This program is copyright (C) 2010 Google, Inc. It is licensed under the Apache License, Version 2.0 Google, Inc. October 18, 2010 RUNLOCK(1)
Check Out this Related Man Page
LOCKF(1) BSD General Commands Manual LOCKF(1) NAME
lockf -- execute a command while holding a file lock SYNOPSIS
lockf [-kns] [-t seconds] file command [arguments] DESCRIPTION
The lockf utility acquires an exclusive lock on a file, creating it if necessary, and removing the file on exit unless explicitly told not to. While holding the lock, it executes a command with optional arguments. After the command completes, lockf releases the lock, and removes the file unless the -k option is specified. BSD-style locking is used, as described in flock(2); the mere existence of the file is not considered to constitute a lock. If the lockf utility is being used to facilitate concurrency between a number of processes, it is recommended that the -k option be used. This will guarantee lock ordering, as well as implement a performance enhanced algorithm which minimizes CPU load associated with concurrent unlink, drop and re-acquire activity. It should be noted that if the -k option is not used, then no guarantees around lock ordering can be made. The following options are supported: -k Causes the lock file to be kept (not removed) after the command completes. -s Causes lockf to operate silently. Failure to acquire the lock is indicated only in the exit status. -n Causes lockf to fail if the specified lock file does not exist. If -n is not specified, lockf will create file if necessary. -t seconds Specifies a timeout for waiting for the lock. By default, lockf waits indefinitely to acquire the lock. If a timeout is speci- fied with this option, lockf will wait at most the given number of seconds before giving up. A timeout of 0 may be given, in which case lockf will fail unless it can acquire the lock immediately. When a lock times out, command is not executed. In no event will lockf break a lock that is held by another process. EXIT STATUS
If lockf successfully acquires the lock, it returns the exit status produced by command. Otherwise, it returns one of the exit codes defined in sysexits(3), as follows: EX_TEMPFAIL The specified lock file was already locked by another process. EX_CANTCREAT The lockf utility was unable to create the lock file, e.g., because of insufficient access privileges. EX_UNAVAILABLE The -n option is specified and the specified lock file does not exist. EX_USAGE There was an error on the lockf command line. EX_OSERR A system call (e.g., fork(2)) failed unexpectedly. EX_SOFTWARE The command did not exit normally, but may have been signaled or stopped. SEE ALSO
flock(2), sysexits(3) HISTORY
A lockf utility first appeared in FreeBSD 2.2. AUTHORS
John Polstra <jdp@polstra.com> BSD
July 7, 1998 BSD