 |
|
Synopsis
da_enterkey
Description
da_enterkey prompts the user for an activation key and creates the license key files at the appropriate directory by executing the license manager command da_elmadmin with the appropriate command line options.
See Also
da_elmadmin
Synopsis
da_startdaemon
Description
da_startdaemon starts the license daemon by executing the license manager command da_elmd with the appropriate command line options.
See Also
da_elmd
Synopsis
da_elmadmin [-b cid -c -C -d -e keydir -h -i -k -l -n -q -r # -s -v # -V [A|B] -x -z] [features | alias | feature = alias,... ]
Description
da_elmadmin is a license administrator program for use with Elan License Manager embedded applications. Its functions include installing license keys, listing the users of licensed products, and other Elan License Manager administrative functions.
Those options marked with an asterisk (*) may only be invoked by: [1] On UNIX the owner of the current license server process, the super-user, or any member of group "wheel" ; [2] On Windows NT, an administrator; [3] On VMS, a user with both WORLD and SYSPRV privileges.
Options
-b cid *
Bury client. Return all licenses used by the client whose client ID is CID, and mark this client as dead. The client ID (CID) may be determined with "da_elmadmin -1".
A buried client will continue to run, but without licenses, and all subsequent functions from the client that communicate with the license server will return an error.
-c
Creates a license key file. da_elmadmin will print a server code which the customer gives to the application vendor who, in turn, will supply a key. Note that a single application may have one or more keys, one for each feature.
If an alias appears as the final argument, then this name will be installed as an alias for this feature. One typically creates an alias for numeric features. Subsequent commands such as "da_elmadmin -l" will print the alias instead of the feature name.
A list of definitions may also appear on the command line. Upon decoding the key input, the feature name gleaned from the key will be matched against the list of definitions. If a match is found, the name following the "=" sign is taken as the feature alias. This provides a convenient way of specifying feature aliases within shell scripts. For example,
da_elmadmin -c -n 01=avalon,02=avaview,03=avaproof
will cause the alias avalon to be selected, if the key decodes with the feature 01.
By default, the key file is placed in the key directory /usr/lib/elm on UNIX systems or SYS$SYSDEVICE:[ELM] on VMS systems, unless the -e option described below is used. In either case, the key directory is not created, but should already exist.
Here are some examples
Send an ELMC_DUMP command to the Elan License Manager daemon da_elmd. This command causes da_elmd to print the contents of the da_elmd database to the log file. It is mostly used for testing and debugging.
-e
This option is only meaningful when the create options -C or -c, described above, are used. By default, license keys are placed in the directory /usr/lib/elm on UNIX systems or SYS$SYSDEVICE:[ELM] on VMS systems. The -e option specifies a different key directory. Thus,
da_elmadmin -e /local/elan -c
will cause the license key to be created in the directory /local/elan on a UNIX system and
da_elmadmin -e dua1:[elan] -c
will cause the license key to be created in the directory dua1:[elan] on a VMS system. Please note that this directory must already exist - da_elmadmin does not create it.
-h
Expanded version of the -l listing, including each client's hold time and the shared license count.
The hold time is the period after the client exits that the licenses will be held (reserved) for the user. If the user starts the application again before the hold period ends, the held licenses will be assigned to him. The hold time is specified in the resource file, see da_elm_resource(5). If the client is held, column one of the listing will be flagged with an "H".
The shared license count is the number of clients that are currently sharing the license for the indicated feature. If the client has one or more shared licenses, column one of the listing will be flagged with an "S".
-i
Prints the release number of da_elmadmin and the release of the Elan License Manager library it was compiled with.
-k *
Kill Elan License Manager daemon da_elmd. The daemon will gracefully terminate upon receipt of the kill request.
-l
Lists the current users and outstanding licenses available for all features known to all license managers on the network. Known features are those features used since the daemon was started (usually the last time the system was rebooted). If features are given on the command line, the listing is restricted to the features named.
Here's an example listing:
CID LID User Feature Group Started
1 1 jon@elan,enzo:0 avalon - May 12 14:45
S 3 2 marcia@elan,mel:0 avalon - May 12 07:13
S 4 2 marcia@elan,mel:0 avalon - May 12 07:13
H 5 3 jeff@trager,unix:0 avalon - Apr 29 09:47
avalon [98]: 50 licenses, 25 in use; installed Feb-12-93.
Expires Jun-12-93.
An "H"' in column one indicates that this client is a held client. Such a client is one that has exited, but the licenses are held for a certain period. Held licenses are discussed under da_elm_resource(5). The hold period may also be listed with the -h option below.
A "D"' in column one indicates that this client is connected but disabled (redundant servers mode, but there are too few servers running currently).
An "S" in column one indicates that this client has a shared license for the indicated feature. Shared license groups share the same LID.
The next field, CID, is the client ID. Each client application will be assigned a unique ID. The CID may be used with the -b option described above.
The LID is the license ID. These are unique license numbers. Each client will normally have unique LIDs for each licensed feature, except when the license is shared. If clients share a license, they share the LID.
The user is displayed as user@host,display where display is the value of the X-11 DISPLAY when the application was invoked. The display may be missing for non X-11 applications.
The -l option scans all servers of the network, as well any defined by DA_ELMHOST.
-n
Generates a numeric-only code. This option should be used in conjunction with the -c option above.
-q
Query. Print various environment information for debugging. Output includes the current host name, its IP address, the name of the DA_ELMHOST environment variable and its current setting, the current port and license service name, the Vendor ID, and the hostcode value.
-r #
Ready-key mode, for use with -c option. Depending on the parameter #, do not print the code(s) or prompt for the key:
If the number # is positive, then do not print the server code(s); only prompt for the server key. The # in this case is the number of servers that will be running, usually 1. (It will be greater than 1 only when backup servers are used.) Thus, "@"-r 1" prompts for a key for a single-server configuration.
If the number # is negative, then no key prompt will be issued; instead only that number of codes indicated will be printed. Thus, "-r -1" prints the current server code but does not prompt for a key.
-s
Find all license servers using server address resolution and print their names. If a feature appears on the command line, the hosts responding with this feature available are printed.
-V version
Set encryption version to the argument, a single character A though E.
-v # *
Change the license manager log file verbose level to #. This may be used to change the level after the daemon has started. See da_elmd(1) for the list of levels and more details.
-x
Inhibit copyright notice.
-z *
Zero log file. One method to clean up the log file every evening on a UNIX system is:
cp elm.log elm.log.old
DA_ELMHOST=somehost da_elmadmin -z
where somehost is the host name where the da_elmd is running.
Alternately, the -m option of da_elmd(1) may be used to automatically keep the log file under control.
Note
that truncating the log file by other means would be ineffectual since da_elmd keeps the log file open at all times. The next da_elmd log file write would simply use the old file pointer, filling the file to the original length. Thus -z of da_elmadmin or -m of da_elmd must be used to truncate the file.
Files
/usr/lib/elm - UNIX default key file directory.
SYS$SYSDEVICE:[ELM] - VMS default key file directory.
See Also
da_elmd(1)
Synopsis
da_elmalert [ -a -b # -e dir -f -h host -m -o percentage -p -u user -x days -v ] [features...]
Description
da_elmalert provides a notification when licenses become available to you or are close to expiration. The command checks the availability/expiration of licenses, and, at your option, either sends mail or prints a message to the screen with the requested information.
da_elmalert may be used if the licensed application does not implement license queuing, or if it is more convenient to receive notification this way. It also may be used by users or system administrators to track license expiration. For example, an administrator can request notification when licenses are within two weeks of expiration.
Normally, you will be notified when each feature mentioned on the command line is available. With the -x option, expiration, rather than availability, is checked. The -a option may be used to only alert you when all of the licenses are available or will expire.
Options
-a
All. If multiple features are named on the command line and the -a option is used, notification will only occur when all the licenses mentioned meet the requested condition--are available or will expire in under the -x specified days. Without the -a option, notification will occur for each feature individually.
-b #
When used with the -f option, check every # seconds, instead of the default 60 seconds.
-e dir
Tell da_elmalert that the key directory is dir, instead of the default /usr/lib/elm.
-f Forever
Normally, da_elmalert checks for the condition once, then exits. With -f, da_elmalert runs until the condition is met.
Under the -f option, once you are notified about a feature, the feature is removed from the checklist. When you have been notified of all feature licenses, da_elmalert exits.
-h mailhost
Specify the host name that supports SMTP mail forwarding. If unspecified, the current host is used.
-m Mail
Mail is sent to the invoker's user name, or the name set via the -u option, if used. This option will only work on systems with an SMTP (Simple Mail Transfer Protocol) service. (See -h option above.)
-o #
Occupancy monitoring. If the number of licenses in use divided by the total number available reaches or exceeds #%, then you will be notified. Thus, "-o 80" warns when license usage has reached 80%. And, "-o 100" warns when no more licenses are available.
-p Print
Information is printed to the screen (stdout) when the license(s) become available or will expire.
-u user
Set the recipient to user for the mail (-m) option.
-v Verbose
Print information about the status of the license(s).
-x days
Without -x, or -o, da_elmalert will notify when licenses become available. If -x is used, notification is instead made if the feature will expire within the specified number of days.
Examples
Send me mail when a license for the feature dorothy becomes available:
da_elmalert -f -m dorothy &
Send "scott" mail if the license for the feature dorothy is within two weeks of expiration.
da_elmalert -m -u scott -x 14 dorothy
Files
/usr/lib/elm - UNIX default key file directory.
SYS$SYSDEVICE:[ELM] - VMS default key file directory.
See also
da_elmrpt(1), da_elmadmin(1).
Synopsis
da_elmd [-D -e path -f -i -l file -m size -n -p # -r file -s # -v # -z #]
Description
The da_elmd command starts the Elan License Manager vendor daemon. This should usually be executed when the system is booted from your system start-up script, usually /etc/rc.local or /etc/inittab on UNIX systems or SYS$MAAGER:SYSTARTUP_V5.COM on VMS systems. On Windows NT, da_elmd must first be installed as a system service with instserv(1), then started with the "net start" command. (See EXAMPLES below.) da_elmd is not yet supported under Windows 3.1. No licensed Elan License Manager application will be able to run if da_elmd is not active.
When running, da_elmd will process client requests, which include issuing and returning licenses, and interfacing with da_elmadmin to list the current users of licensed applications.
For each Elan License Manager licensed application, there are one or more key files. These files are expected in a key directory. The key directory or directories may be specified with the -e option to da_elmd, described below.
The key directory may also be specified with the application's -e option. Key files may be freely installed or updated while da_elmd is running--they will automatically be re-read if da_elmd detects a modification date change.
The key file itself has the same name as the feature. The file is usually created by da_elmadmin(1) when the application is first installed via a command of the form:
da_elmadmin -n -c alias
If an alternate key location is desired, the command would instead be:
da_elmadmin -e keypath -n -c alias
Refer to da_elmadmin(1) for other options.
Each key file contains the encrypted key, which encodes the feature name, the maximum number of licenses available for the feature, and the feature's expiration date. The manager da_elmd(1) reads this key and will not issue more licenses than indicated or past the expiration date.
Options
-D Debug mode:
da_elmd runs with the current working directory set to /.
Please also see the -v flag below for changing the verbosity level of da_elmd.
-e path
Optionally specify the key directory, or set of directories, and load all keys found in the directories.
On Windows, directories are specified as a semicolon (;)-separated list of directory names. For example:
da_elmd -e \local\elan;\local\express;\usr\lib\elm
will cause da_elmd to load the key files in the directories /local/elan, /local/express, and then /usr/lib/elm, in that order. On UNIX systems, directories are specified as a colon (:)-separated list of directory names. For example:
da_elmd -e /local/elan:/local/express:/usr/lib/elm
On VMS systems, directories are specified by a comma (,)-separated list of directory names. Thus,
da_elmd -e DUA1:[ELM],DUA1:[EXPRESS],DUA0:[LOCAL]
will cause da_elmd to look for a key file in the directories DUA1:[ELM], DUA1:[EXPRESS], and then DUA0:[LOCAL], in that order.
A key directory may also be specified with the application's -e option. If so specified, the client's key directory is searched first, followed by those specified with -e, if any.
Note that there is no default key path. Therefore, if the -e option is not specified, there is no key path defined and the client must set the key directory name, using the application's -e option.
-f
Normally on UNIX, da_elmd will run in the background (it forks a child process, detaches from the terminal, and the parent exits). The -f option inhibits this, and causes da_elmd to run in the foreground. One may, for example, wish to run da_elmd from inittab, instead of /etc/rc.local, with the -f option.
On VMS systems, da_elmd always runs in the foreground. To get da_elmd to run in the background, use a command like
RUN/DETACHED/PROCESS=DA_ELMD/INPUT=cmdfile -
/OUTPUT=logfile SYS$SYSTEM:LOGINOUT.EXE
where cmdfile is the name of a command file containing the da_elmd command and logfile is the name of a file to which any error messages should be written.
-i
Print the Elan License Manager release number, the vendor ID, and exit. The vendor ID provides a way to verify that the same vendor salt is being used among all the Elan License Manager commands. The vendor ID should be the same for da_elmd, da_elmadmin, etc.
-l file
Creates a log file named file and writes all relevant information to that file. If the file already exists, da_elmd will append to the end of the file. Note that file must be a complete path name.
Use of a log file is highly recommended, as it provides a way of tracking problems if they occur. A log file must be enabled for da_elmrpt(1) to provide reporting information. Please see also -m option below.
-m size
Limits the log file to the size specified. With this option, the log file is "self maintained" by da_elmd such that da_elmd limits the size that the log file may grow to. When this size is reached, the log file named file is moved to file.old on UNIX systems or file_old on VMS systems and the current log file is truncated.
The size is an integer or floating-point number. The default units are bytes. It may also be specified in kilobytes by suffixing a "k" or megabytes by suffixing an "m"' to the size.
For efficiency, the log file size is actually checked only every 100 lines, so it might grow a bit beyond the limit before it is backed up and truncated.
-n
Non-networked (standalone) operation (not applicable for Windows). This tells da_elmd(1) that there is no network and to use local communication only. (This will force da_elmd to use DEC Mailboxes on VMS or System V native interprocess communication on UNIX.) This option is applicable on VMS without DECNET and small UNIX systems such as SCO and Interactive UNIX without TCP/IP installed. This option is unnecessary on Windows.
When -n is used with da_elmd(1), the DA_ELMHOST environment variable must be set to "LOCAL". (On VMS "NO_DECNET" is a synonym for "LOCAL" for backwards compatibility.)
Note that on System V, the default interprocess communication queue is quite small; adequate for about two client processes talking to da_elmd concurrently. da_elmd will attempt to increase the queue size, but, since only root can raise the IPC queue size, it must be run as super-user to be effective.
-p #
Causes da_elmd to use the port address # instead of the default address or one specified by the system service. One might use this option if there was a port address conflict and the user did not have permission to alter the system port services file.
-r file
Issues licenses to the users according to the specifications in resource file. See da_elm_resource(5) for an explanation of this file's format. Note that if this file is changed, da_elmd will automatically reread it--it is not necessary to restart da_elmd.
-s #
Set the start-up time to # in seconds. This is the period that da_elmd waits and listens for client reconnects after a possible crash. The default is 180 seconds (3 minutes.) If you are not on a network, this may be set to zero.
-v #
Select the verbosity of the messages printed to the log file. When a level is selected, all levels less than or equal to the level are printed. Levels 5 and higher are considered debugging levels. da_elmd starts in level 3. The levels are:
1 - Only error messages
2 - License failures
3 - License activity
4 - Client connects and disconnects
5 - Message for every packet received
6 - Message for every packet sent
7 - More client and zombie information
8 - Info about key and resource file
9 - Major stuff
-z #
Set the zombie to # seconds. If a client is not heard from within this time period, it is declared dead and its licenses are returned. The default zombie interval is 3 minutes. Note that da_elmd only cleans up zombies every 60 seconds, so it may take up to 1 minute more for the licenses to be returned.
Example
Here is an example invocation of da_elmd which might appear in the UNIX system start-up file /etc/rc.local. It sets the log file to /usr/adm/elm.log and limits the log file size to 1/4 megabyte.
if [ -f /etc/da_elmd ]; then
echo "`/etc/da_elmd -i` started." > /dev/console
/etc/da_elmd -m 0.25m -l /usr/adm/elm.log > /dev/console
fi
Here is an example invocation of da_elmd which might appear in the VMS system start-up file SYS$MANAGER:SYSTARTUP_V5.COM. It sets the log file to DUA1:[ELM]ELM.LOG and limits the log file size to 1/4 megabyte.
$ RUN/DETACHED/PROCESS=DA_ELMD/INPUT=SYS$MANAGER:DA_ELMD.COM -
/OUTPUT=OPA0: SYS$SYSTEM:LOGINOUT.EXE
where the command file SYS$MANAGER:DA_ELMD.COM contains
$ DA_ELMD := $SYS$SYSTEM:DA_ELMD.EXE
$ DA_ELMD -M 0.25M -L DUA1:[ELM]ELM.LOG
On Windows NT, the daemon must first be installed as a system service before it can be started. See instserv(1) for one way to install a new system service. Once installed, the service can be started and stopped with the commands "net start" and "net stop" respectively. For example, if da_elmd has been installed as a new service under the name "MegaSoft License Manager", then to start the service with log file C:\megasoft\elm.log and immediate start-up, you would type:
net start "MegaSoft License Manager" /s0 /lC:\megasoft\elm.log
Note the use of "/" rather than "-" as the switch delimiter; net start ignores switches not prefaced by a "/".
If you are using a log file (which is highly recommended) you will need to trim it every so often. This can be done automatically with the -m option of da_elmd, or via a nightly daemon spawned from crontab on a UNIX system or a nightly batch job on a VMS system and the -z option of da_elmadmin. The -m variation was illustrated above. Below is an example pair of commands to keep the log file under control with the nightly crontab scheme:
cp /usr/adm/elm.log /usr/adm/elm.log.old
DA_ELMHOST=somehost da_elmadmin -z
where somehost is the host name where the da_elmd is running. Following is a sample batch command file to control the log file size on a VMS system:
$ COPY DUA1:[ELM]ELM.LOG DUA1:[ELM]ELM.LOG_OLD
$ DA_ELMHOST = somehost
$ DA_ELMADMIN -Z
where somehost is the host name where the da_elmd is running.
See Also
da_elmadmin(1).
Synopsis
da_elmrpt [ -d daterange -f feature -h -i -l -t -u category -w # ]
[ logfiles | logfiledirs ] ...
Description
da_elmrpt produces a report of licenses available or license activity from one or more license server log files, given, as its argument, as a list of file names or directories containing log files. The default log file is /usr/adm/elm.log on UNIX systems and SYS$MANAGER:ELM.LOG on VMS systems. da_elmrpt may be used with log files from all releases of Elan License Manager as well as an older licensing system called Flexlm, and completely merged reports will be generated.
See da_elmadmin(1) (-l option) and da_elmusage(1) for a snapshot of current license activity.
da_elmrpt can display its information in two formats: numerically and as a histogram. Here is sample of numeric output from da_elmrpt -t day:
Feature Requests Issued Denied %-Denied Total Time Used
Apr 14|avalon 46 46 0 0% 0d 12h 02m 27s
Apr 15|avalon 6 6 0 0% 0d 18h 40m 03s
Apr 16|avalon 60 4 6 10% 1d 03h 35m 21s
Apr 17|avalon 3 3 0 0% 0d 00h 23m 14s
Apr 18|avalon 4 4 0 0% 0d 00h 21m 11s
Apr 19|avalon 26 26 0 0% 0d 07h 08m 34s
The Requests column shows the total number of license requests for the Feature. The Issued column shows the number of licenses successfully issued, and the Denied column shows the number denied, most likely from the maximum number of licenses being already in use. The %-Denied column indicates the frequency of denied licenses out of the total number of requests. The final column shows the total time that the feature was checked out by application(s).
The default report is detailed per feature. Reports can be further detailed by user, user@host, and/or numeric output when da_elmrpt is used with the -uu (display-by-user) option:
|Feature Requests Issued Denied %-Denied Total Time Used
Feb 9|avalon 34 29 5 15% 0d 04h 44m 50s
| jim 20 16 4 20% 0d 00h 00m 30s
| carol 5 5 0 0% 0d 04h 40m 10s
| bob 1 1 0 0% 0d 00h 04m 10s
Feb 10|avalon 9 9 0 0% 0d 12h 10m 27s
| jim 1 1 0 0% 0d 12h 00m 10s
| bob 2 2 0 0% 0d 00h 10m 17s
Use of the -h option produces a histogram instead. Here is a sample of a histogram from da_elmrpt -h -t day:
Feature * = issued, o = denied
Apr 14|avalon ********************************** |46
Apr 15|avalon **** | 6
Apr 16|avalon ********************************************ooo |54
Apr 17|avalon ** | 3
Apr 18|avalon *** | 4
Apr 19|avalon ******************** |26
When displayed as a histogram, the number of successful requests is displayed as a series of asterisks ("*") and denied requests as a series of "o"s ("o"), followed by the actual number of successful requests. The graph is normalized for a screen width of 78, which may be adjusted with the -w option.
Here's a further example, using the detail-by-user option (-uu):
Feature * = issued, o = denied
Apr 14|avalon *************** |46
| janett ******************** |41
| ken ** | 3
| roesner * | 2
Apr 15|avalon **** | 6
| janett *** | 4
| ken * | 2
Apr 16|avalon ****************** |61
| janett **************************** |59
| lynn * | 2
A summary of licenses installed may also be obtained with the -l option. The summary will be sorted by the feature alias. Here's an example:
Feature Tokens Expiration Key File
WordSmart 500 /usr/lib/elm/50
Express 75 /elan/express/key/10
MultiC 250 Nov 30 10:00:00 1994 /elan/express/key/1
Options
-d [ from - to | from ]
Limit reporting for dates between from and to inclusive. The from and to dates may be specified in one of two formats:
Feb 3 12:30:00
2/3 12:30:00
In the first format you specify the first three letters of the month. The second form, the month number, followed by a slash is used. For example:
Note that in either format, only the month is required--the day, hour, minutes, and seconds will default to zero if missing. If the hyphen and to date are missing, the report will run to the last date.
-f feature
Only lists activity for the feature named. Multiple -f options may be used to limit display to several features.
-h
Prints a usage histogram instead of numeric data. (See also -w option below.)
-i
Prints the release number of da_elmrpt and the release of the Elan License Manager library it was compiled with, then exits.
-l License listing.
Displays a summary of Elan License. Manager licenses available along with the number of tokens of expiration dates if any. No other options are meaningful with -l.
-t timeunit
Displays total license activity for each timeunit, where timeunit may be month, day, hour, minute, second. (A unique abbreviation, such as "min", is ok.) For example:
da_elmrpt -d "3/15 - 4/15 5:30" -t hour
If the -t option is not specified, a grand total only is printed.
-u category
Details report by each user, as specified by category. The category may contain one or more key letters "u", "h", and "d" for user name, host, and display, respectively. Key letters may be combined in any combination of one to three letters. For example, -uu details per user name only; -uh details per host name only; and -uuh provides more detail, with results displayed for each distinct user@host.
-w #
Specify a display width of # character units. The default is 78. This option is currently only effective with the -h (histogram) option.
The remaining arguments are zero or more license server log file names or directories. If any argument is a directory, then all log files in that directory are digested. da_elmrpt will silently skip files that are not license manager log files.
If no files are specified on the command line, then the default /usr/adm/elm.log, or SYS$MANAGER:ELM.LOG on VMS will be used.
Files
/usr/adm/elm.log - UNIX default log file.
sys$manager:elm.log - vms default log file.
Caveat
The "Total Time Used" field will be valid only for Elan License Manager log files from release 2.3 and above or FlexLM log files for which time logging has been enabled.
See Also
da_elmalert(1), da_elmusage(1), da_elmadmin(1), da_elmd(1)
Synopsis
da_elmusage [ -b seconds ] [ features ... ]
Description
da_elmusage produces a snapshot report of current license activity, updating every 10 seconds. Here is sample output from da_elmusage:
License activity on elan:
Feature in use total occupancy
------- ------ ----- ---------
express [01] 224 250 90%
avalon [01] 400 400 100% ****
For each feature in use (or in past use), a line is printed with the current number of licenses in use, the total number of licenses available, and the current occupancy--the percentage of in-use licenses divided by the total number. A high percentage indicates that it might be wise to purchase additional licenses. If occupancy hits 100%, a series of asterisks are printed in the right column.
Options
-b n
Change the interval to n seconds, from the default 10.
features
Examine only the features named, instead of all features.
See Also
da_elmrpt(1), da_elmadmin(1), da_elmd(1)
Synopsis
da_elmver [-v] files...
Description
da_elmver scans the files named for the Elan License Manager version string and(if the -v option is used) other version information, and displays it, if found. It will be displayed in the form:
file: Elan License Manager release 2.2.3
If the -v option is used, a message of the following form will be printed:
file: Elan License Manager release 2.3.0
file: HAVE_SIG=SIGACTION
file: HAVE_IDPROM=GETHOSTID
file: HAVE_ETHER=TRUE
The supplemental version information may change from release to release. Currently, we display which signal handling function is used, how the ID Prom is determined, and if the Ethernet address is available or not for host locking.
Only files compiled with the Elan License Manager library that does any license server communications will automatically have the version information compiled into it. Running da_elmver on the Elan License Manager library is always a sure bet.
da_elmver is handy for determining the release level of the Elan License Manager library that a command was compiled with. However, for the convenience of you and your customer, we also recommend that you display the Elan License Manager release number wherever you display your product's release number.
Caveat
da_elmver works only on files compiled with the Elan License Manager library and that do server communication.
Options
-v Verbose
Display additional version information.
Description
The resource file contains Elan License Manager-related resource information. The file currently may be used to specify:
#"' at the beginning of any line will be treated as a comment; the remainder of the line is ignored.
To use the resource file, the license manager da_elmd(1) must be started with the -r option.
Packet Filtering (domain restricting)
By default, the Elan License Manager accepts requests from any IP address. If desired, requests may be limited to only those addresses that conform to your specification. For example, if your company owned a Class-A network, but was also on the Internet, you might wish to limit license server requests to only those on your Class-A network domain.
Packet requests may be limited to machines defined by an IPACCEPT mask specified in the resource file.The mask may appear in the resource file as a line of the form:
%IPACCEPT mask
where mask is a 4-tuple of expressions "e", separated by periods: "e.e.e.e.".
Each e may be any one of the following, or a comma-separated list of any of the following:
For example, a mask of :
THIS.*.*.*
would limit requests from only those on the same Class-A network as the license server. Also,
THIS.100,200-224,226.*.*
would limit requests from only those on the same Class-A network and from Class-B subnetworks 100, 200 through 224, and 226.
Elan License Manager may be run with one or more license servers to implement server redundancy (backup servers.) In the redundancy model, each server host should be named in the resource file. The server names are listed via lines of the form:
%SERVER hostname
where hostname is the name of one of the redundant hosts.
The %SERVER definitions are required only for use with redundant servers; they are unnecessary when the single server model is used.
Note that redundant keys must also be used.
Reserved/Excluded/Held licenses
Feature licenses may be reserved to individual users or client machines via the Elan License Manager resource file. Individual users and/or client machines can also be excluded from using specified features. Reserved and excluded licenses are indicated in the resource file via lines of the format:
feature:group:client1,...,clientn:k:h
The individual items of each line are:
Note that the held period is determined from the resource file as follows: (1) If the license requested comes from the reserved license pool for a group, it will have the group's hold period. (2) If the license requested comes from the free license pool, the first line that matches the feature and group member will contain the hold time that is used. Therefore, order in the resource file may be important. (See the example below.)
Example
Here's a sample resource file (using every feature we could think of):
# Accept requests from this Class-C network only.
%IPACCEPT THIS.THIS.THIS.*
# We're using 3 redundant servers.
%SERVER hoss
%SERVER ben
%SERVER littlejoe
# Our reserved and excluded licenses...
99:mother-in-law:harriet,@wanda:EXCLUDE:0
99:wordproc:wendy,diane,jon,paul:3:600
99:hackers:jeff,sara,tom:3:120
99:lab:@enzo.elan.com,@trager.elan.com:1:0
# Everyone else has a default hold period of 60 seconds 99:default::0:60
In this example resource file,
Also, the hold period has been assigned as follows:
Order of the lines is relevant: (1) EXCLUDED lines should come first; (2) If both host names and user names are used, the first match, host or user name, from left to right and top to bottom is used; (3) A default hold time should be indicated last.
Thus, in our example above, if Wendy, while logged into machine enzo.elan.com, checked out a license for 99, her license would come from group wordproc, rather than lab, since that entry appears first in the resource file.
See Also
da_elmd(1)
da_elmadmin
| |
|