By Saker Klippsten -
Before I submit a ticket to The Foundry I need a sanity check.
We use the FOUNDRY_LICENSE_FILE system variable and we specify two
servers separated by a ";" per their installation instructions. We do
this to share the licenses between facilities. ( The foundry allows
for this ). If one server is tapped out the next server will issue
licenses but I am running into an odd behavior.
Variable name: FOUNDRY_LICENSE_FILE
Variable value: siteA;siteB
1. User Starts up Nuke and attempts to pull a floating lic from Site A
because siteA is listed first as the value
2. User gets denied a license from Site A
3. User Gets license from siteB and gets a license.
4. User decides to open another instance of Nuke.
a) If the user presses control-n to open another instance, nuke will
open - using the current license server and therefore not pull a new
license.
b) if the user uses the desktop shortcut to open another instance of
nuke and there is a license available on siteA Nuke will pull another
license.
Nuke opens but is actually pulling another license from Site A because
a license was now available on siteA.
Now the user is pulling two licenses. One from Site A and one from
Site B. Instead of just the initial License from Site B.
What this tells me is two things.
1. When starting another instance of Nuke via the shortcut. Nuke (
client side) does not look where it is currently pulling a license
from and attempt to communicate with that server. If that were the
case the server would say User! you have a license issued already, go
ahead and open another instance of nuke free of charge the same way it
does if you press control-n
Instead Nuke just round robins through the site Variables specified
and if there happens to be a license free the next time you go to open
another instance of Nuke it will pull it.
To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe
↧