HPlogo HP-UX Reference Volume 2 of 5 > i

i4lmd(1M)

LicensePower/iFOR Version 4.0
» 

Technical documentation

Complete book in PDF

 » Table of Contents

 » Index

NAME

i4lmd — starts the license server on a local node

SYNOPSIS

i4lmd [-s[ecure]] [-l[ogname]] [-v[erbose]] [-z[debugging]] [-n[o] event_types] [-c[oldstart]]

DESCRIPTION

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 run manually.

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.

Options

-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.

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 deleted.

p

Product events: a product was added, renamed, or deleted.

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 startup.

EXAMPLES

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:

i4lmd -c

Start a license server, overriding the default log file:

i4lmd -l /logs/license_server_log

AUTHOR

i4lmd is a product of Isogon Corporation.

FILES

/opt/ifor/ls/bin/i4lmd

/opt/ifor/ls/bin/i4config

/opt/ifor/ls/doc/i4admin.pdf

LicensePower/iFOR Administrator's Guide (Adobe Acrobat format)

/opt/ifor/ls/doc/i4admin.ps

LicensePower/iFOR Administrator's Guide (postscript format)

SEE ALSO

i4admin(1M), i4start(1M), i4stop(1M), i4target(1M), i4tv(1M), LicensePower/iFOR Administrator's Guide.

© Hewlett-Packard Development Company, L.P.