User guide

Chapter 5 - The Options File
Rules of Precedence in Options Files
62 FLEXnet Licensing End User Guide
FLEXNET LICENSING VERSION NOTES
•The lmreread utility enhanced in v8.0 vendor daemon so that it causes the vendor daemon
to reread the options file. If you are using earlier versions, the vendor daemon must be
stopped and restarted in order for the options file to be reread.
Rules of Precedence in Options Files
Rules of precedence take effect when INCLUDE and EXCLUDE statements are combined in
the same options file and control access to the same features. The following define the
precedence when both types of statements appear together:
• If there is only an EXCLUDE list, everyone who is not on the list is allowed to use the
feature.
• If there is only an INCLUDE list, only those users on the list is allowed to use the feature.
• If neither list exists, everyone is allowed to use the feature.
• The EXCLUDE list is checked before the INCLUDE list; someone who is on both lists is
not allowed to use the feature.
Once you create an INCLUDE or EXCLUDE list, everyone else is implicitly outside the group.
This feature allows you, as an administrator, the ability to control licenses without having to
explicitly list each user that you wish to allow or deny access to. In other words, there are two
approaches; you either:
• Give most users access and list only the exceptions, or
• Severely limit access and list only the those users that have access privileges
Options File Examples
The following information gives some examples of options files intended to illustrate ways to
effectively control access to your licenses.
Simple Options File Example
RESERVE 1 compile USER robert
RESERVE 3 compile HOST mainline
EXCLUDE compile USER lori
NOLOG QUEUED
This options file:
• Reserves one license for the feature “compile” for the user “robert.”
• Reserves three licenses for the feature “compile” for anyone on the system with the host
name “mainline.”