Options File
| file. However, there might be other license daemons managing other license |
| files. lmgrd runs on the license host. |
| ` Vendor daemon (prold) — Works with lmgrd to dispense tokens. Each |
| feature of a floating (development client) license has a limited number of |
| tokens. |
License Types | Two types of licenses are available with Prolifics; each type is specific to the |
| component installed: |
| ` A Prolifics web application server uses a license type that allows for an |
| unlimited number of application servers to run on a specific computer. The |
| license does not require a license daemon. This type of license is referred to as |
|
|
| ` Prolifics UNIX clients use floating licenses. This type of license is not |
| associated with a particular machine, but is assigned by the license server to |
| each Prolifics development client when the executable is run. This license type |
| requires a license daemon. |
| Note: Because a floating license is associated with the Prolifics development |
| executable, and not with an actual machine, it is possible for a developer to |
| use more than one license. For example, if a developer is running two Prolifics |
| sessions simultaneously on one machine, the license manager assigns two |
| licenses, not one. |
Options File
The daemon options file allows you to customize Prolifics license usage at your site. The information in the file can specify such information as:
`Which users or groups of users can use Prolifics.
`Which messages will be included in the log file.
`How long a copy of Prolifics will remain idle before timing out.
There is no default location or name for the options file. If used, its name appears as the fourth argument on the DAEMON line of the license file license.dat, in the optional field
Appendix C License Administration | 59 |
