TO BE OBSOLETED
i4lmd - starts the license server on a local node
i4lmd [-s[ecure]] [-l[ogname]] [-v[erbose]] [-z[debugging]] [-n[o]
The i4lmd command starts a license server on the local node. There is
no graphic interface for this command, the shell script i4config is
used to configure the license server. License servers should not be
A printable on-line administration guide is also available. (See the
FILES section below.)
NOTE: Please refer to the release notes and i4config for information
on how to automate the start-up of i4lmd on your specific platform.
-s Secure mode. A LicensePower/iFOR license server running
in secure mode will only permit modifications to its
database from tools run locally (on the same node).
Tools running on remote node are not permitted to
modify the database.
-l log_name Redirects license server log entries to a file and
location other than the default
(/opt/ifor/ls/conf/logdb*). The alternate log file
specification (filename) must be fully qualified
starting from the root directory (/).
-v verbose The verbose flag should only be used by administrators
the event of a server failure. This command allows the
administrator to review license calls and activity from
the client programs. The -v option is used in
conjunction with -z.
-z debugging The debugging flag allows the administrator to review
all rpc communication between the clients and the
server. The -z option is used in conjunction with -v.
-no Turns off logging of the events specified in
event_list. Any combination of events is valid, but
items in the list of events must not be separated by
spaces or other characters. Following are the event
types that you may specify:
l License-grant and license-release events.
Hewlett-Packard Company - 1 - HP-UX Release 11i: November 2000
TO BE OBSOLETED
c License checkin events. (Licensed products usually
check in with the license server at regular
intervals while a user is using the product).
w Waiting events: these include wait events (a user
was waiting for a license), waitgrant events (a
user was waiting for and then was granted a
license), and waitremove events (a user was
waiting for a license and then asked to be removed
from the queues before a license was granted).
v Vendor events: a vendor was added, renamed or
p Product events: a product was added, renamed, or
e Error events.
t License timeout events. (When a licensed product
fails to check in with the license server, it may
stop running after it "times out." The vendor of
the product sets the timeout interval, which is
how long a product may run after it has lost
contact with the license server).
m Message events.
s License server start/stop events.
-c This option will delete all transactions records from
the database and subsequently that cache during server
Start a license server; do not log checkin, vendor, product, timeout,
or message events:
i4lmd -no cvptm
Start a license server, deleting all transactions from the database:
Start a license server, overriding the default log file:
i4lmd -l /logs/license_server_log
LSSERV Software Obsolescence
HP intends to remove LicensePower/iFOR from the core HP-UX product in
Hewlett-Packard Company - 2 - HP-UX Release 11i: November 2000
TO BE OBSOLETED
a future release. The licensing product can be obtained directly from
Isogon Corporation, the owner of the product.
For further information about LSSERV support, see the Isogon
Corporation website at http://www.isogon.com.
Competitive information is also available at these websites:
FLEX/lm via http://www.globetrotter.com
SentinelLM via http://www.rainbow.com
Administrator's Guide (PDF
i4lmd was developed by HP and Gradient Technologies, Inc. It is
currently a product owned by Isogon Corporation.
i4admin(1M), i4start(1M), i4stop(1M), i4target(1M), i4tv(1M).
LicensePower/iFOR Administrator's Guide available in /opt/ifor/ls/doc/
in PDF format.
Isogon Corporation information on LicensePower/iFOR at:
HP-UX documentation at http://docs.hp.com.
Hewlett-Packard Company - 3 - HP-UX Release 11i: November 2000