next up previous contents index
Next: gidd_alloc Up: 11. Command Reference Manual Previous: filelock_midwife   Contents   Index

Subsections


filelock_undertaker

determine whether a process has exited

Synopsis

filelock_undertaker -help

filelock_undertaker [-file filename] [-block]

Description

filelock_undertaker can examine an artifact file created by filelock_midwife and determine whether the program started by the midwife has exited. It does this by attempting to acquire a file lock.

Be warned that this will not work on NFS unless the separate file lock server is running.

Options

-block
If the process has not exited, block until it does.
-file filename
The name of the artifact file. created by filelock_midwife. The file lock.file is the default file used when this option is not specified.

Exit Status

filelock_undertaker will exit with a status of 0 (zero) if the monitored process has exited, with a status of 1 (one) if the monitored process has definitely not exited, with a status of 2 if it is uncertain whether the process has exited (this is generally due to a failure by the filelock_midwife), or with any other value for program failure.

See Also

uniq_pid_undertaker (on page [*]), filelock_midwife (on page [*]).

Author

Center for High Throughput Computing, University of Wisconsin-Madison

Copyright

Copyright © 1990-2013 Center for High Throughput Computing, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved. Licensed under the Apache License, Version 2.0.

See the HTCondor Version 7.9.6 Manual or http://research.cs.wisc.edu/htcondor/ for additional notices.


next up previous contents index
Next: gidd_alloc Up: 11. Command Reference Manual Previous: filelock_midwife   Contents   Index
htcondor-admin@cs.wisc.edu