Message-ID: <1175493145.8771.1711697107876.JavaMail.confluence@host3.pipelinefx.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8770_1858530680.1711697107876" ------=_Part_8770_1858530680.1711697107876 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Per-host license resources are similar to the original license r= esources in that they act exactly like global resources with the added bene= fit of being dynamically updated in the Supervisor by an external applicati= on. Per-host license resources differ from the original license resources i= n that the resources are consumed on a per-host basis, just like the per-ho= st global resources.
Per-host license resources are also defined on the Supervisor using the =
qb.conf file, using the configuration parameter supervisor_global_resources=
, as in:
supervisor_global_resources =3D resspec [,
The resspec in this case uses the keyword license_host:
&n=
bsp; license_host.name=3Dquantity=
where name is the name of the resource, and quantity i= s the total number of named resources available.
As with the original license resources, per-host license resources requi= re the use of an external application to monitor the state of the license s= erver, to update the Supervisor on a regular basis to ensure the Supervisor= is fully aware of the actual number of licenses available.
Here is an example for a site that has twenty licenses for Nuke:
<=
code>supervisor_global_resources =3D license_host.nuke=3D20
and an example call to qbupdateresource that a total 20 licenses are ins=
talled, and 12 are currently in use:
% qbupdateresource =E2=80=
=93name license_host.nuke -total 20 -used 12