{section: Lease Manager Daemon}
-The Lease Manager, as its name implies, is a Condor daemon that manages
-the leasing of some type of resource within the confines of a Condor
+The Lease Manager, as its name implies, is a HTCondor daemon that manages
+the leasing of some type of resource within the confines of a HTCondor
pool. What the resource represents is immaterial to the lease manager;
it could be software licenses, disk space, or network I/O.
A lease manager daemon can handle one type of resource. You would
@@ -9,7 +9,7 @@
want to represent.
The architecture of resource leasing is very similar to the matching of
-machines with jobs in Condor. Offers of and requests for a resource are
+machines with jobs in HTCondor. Offers of and requests for a resource are
represented by classads. The ads are matched with each other, with each
ad able to provide a requirements expression that constrains what it can
be matched against. Resource offers are advertised in the collector by
@@ -52,12 +52,12 @@
after a failure.
The lease manager is used by some portions of stork, but isn't used
-anywhere in Condor currently. It's included in the Condor release.
+anywhere in HTCondor currently. It's included in the HTCondor release.
There are some tests for it in the test suite, one of which is run in
the nmi build/test cycle.
Configuration parameters used by the lease manager are documented in the
-Condor manual.
+HTCondor manual.
{subsection: Questions}
*: What attributes are defined for the various ads used by the lease manager?
