runlock - prevent concurrent execution of a process

runlock was written by Jamie Wilkinson <jaq@google.com>.

       Sending SIGALRM to runlock before the timer has expired will cause the subprocess to be killed.

       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)

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
       failure exit code. Otherwise, the exit code of the subprocess is returned.

       runlock - prevent concurrent execution of a process

runalarm(1), runstat(1)

runlock [ -h ]

       runlock [ -d ] [ -fpathname ] [ -ttimeout ] command [ args ]

-d

              Debug mode; send log messages to standard error as well as to the system log.

       -fpathname

              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".

       -ttimeout

              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.