Page History

Description | Usage | Options | Examples | Notes | See also

...

• you own 100 prman licenses
• Qube is configured to allow up to 100 prman job instances to be running at any one time by defining license.prman=100 (see System-wide Resource Tracking and License Resources).

...

• The supervisor will then assume that there are 20 licenses in use by some external entity, will set the resource usage for license.prman to 80, and the only dispatch up to

Usage 

Options

Notes

Examples

See also

NAME
qbupdateresource - sets the external resource values of the supervisor

SYNOPSIS
qbupdateresource --total [total] --used [used] --name [name]

DESCRIPTION
qbupdateresource sets resource values of an external resource.

...

–total flag behavior explained

The -total value you give it via the "qbupdateresource" command specifies the grand-total number of licenses, while the value you specify in the qb.conf file's supervisor_global_resources parameter refers to the total (maximum) number that the farm may use.

So, for instance, if you have in qb.conf:

supervisor_global_resources=license.maya=100

and you run qbupdateresource as in:

qbupdateresource -total 120 -used 80 -name license.maya

you're essentially saying that you have 120 grand-total count of licenses in your studio, while you're allowing the farm to use up to 100 of them. The remaining 20 is reserved for the use outside of the farm.

If, in the above scenario, all the 80 "used" licenses are being used on the farm, then qbadmin s -resource will display:

license.maya=80/100

Note that the denominator is still 100, because that's the number allotted to the farm.

If 70 is used on the farm, and 10 outside, then:

license.maya=70/100

If, on the other hand, say 50 is being used on the farm, and 30 outside, then "qbadmin s -resource" will display:

license.maya=60/100

That's because the "outside" count has gone over its "reserved" amount of 20, and 10 bleed into the farm allocation. 

Notes

Examples

See also