Internal: How many concurrent IDL sessions can be started from a "single-user" license?
Anonym
Topic:
This article contains a description of FLEXlm license availability for RSI products. In general, a single-user (a.k.a one
"license seat") node-locked or floating RSI product license can support any number of concurrent product sessions as long as the the session processes are run on the same machine, owned by the same username and are all displayed to the same display specification.
This concepts applies to RSI products on both Windows and UNIXes (including Linux and Mac OS X)
One RSI product license seat permits multiple concurrent product sessions as long as:
1. All of the sessions are run on the same system/machine
2. All sessions have the same process owner
3. All of the sessions are displayed to the same display |
Details about IDL's "license seat" implementation are discussed below. The concepts also apply to other RSI products such as ENVI and IDL Runtime.Discussion:
UNIX, LINUX, MAC OS X:
A single user IDL
license seat on UNIX / Linux / Mac OS X will license any number of concurrent IDL sessions as long as the following three parameters are the same for each of the running IDL sessions:
- The system/machine that is hosting the IDL process.
- Username/owner of the IDL process.
- DISPLAY system environment variable definition.
For example, suppose the following four IDL sessions are started and are running simultaneously. In this case ont 3 IDL license seats would be taken by these 4 processes. See comments for details.
|
|
|
|
| 1 |
| Hostname: |
MachineA |
| Username: |
joe |
| DISPLAY definition: |
"MachineA:0" |
|
| In this example, concurrent Sessions 1 and 2 occupy only one IDL license seat because each of the three parameters (Hostname, Username and DISPLAY environment variable definition) are the same for both IDL sessions. |
|
| 2 |
| Hostname: |
machineA |
| Username: |
joe |
| DISPLAY definition: |
"MachineA:0" |
|
| 3 |
| Hostname: |
machineA |
| Username: |
mary |
| DISPLAY definition: |
"MachineA:0" |
|
| Session 3 occupies a second IDL license seat because the username is different than in sessions 1 and 2. |
|
| 4 |
| Hostname: |
MachineA |
| Username: |
joe |
| DISPLAY definition: |
"MachineA:1" |
|
| Session 4 occupies still another IDL license seat this time because the DISPLAY system environment variable definition string is different than in sessions 1 and 2. |
|
WINDOWS:
On Windows, a similar license seat model applies for multi-user systems, such as Windows Terminal Server machines. However, instead of the UNIX DISPLAY system environment variable definition, the Windows session display host value is used as the third parameter to determine license seat usage. That is:
- The system/machine that is hosting the IDL process.
- Login name/owner of the IDL process.
- Windows session display host
Solution:
[Edit this field in the IDL-based Tech Tip Editor, v60]