testlicense

Daylight v4.9
Release Date: 1 February 2008

Name

testlicense - verify that a Daylight license is valid.

Unix Synopsis

testlicense [-i|-v|-t|-p|-s name]

Description

testlicense invokes Daylight's license-checking functions to verify that a Daylight license is valid. It has three uses:

To verify that a newly-installed system's license is valid and the environment variables (e.g. DY_ROOT) are correct.
In shell scripts and makefiles to test for specific licenses, such as to decide whether or not particular program should be compiled.
During installation, the "-i" option will print the CPU ID information needed for your license (see below).

Options

-i

Don't check the license; instead, print the identifying information for this particular machine (e.g. for the "cpu type:" and "cpu idno:" lines of the license file). The output is suitable for using directly in the license file.

-v

Give verbose information about the license processing, including the license sources used and the complete set of features licensed. In the case of FLEXnet license features, the license availability and if present, Daylight server and database connection counts are provided. Available FLEXnet license modules are indicated with the plus sign, "+" while unavailable modules are marked with a minus sign, "-". This option is extremely useful for debugging.

-t name

Test if Daylight Toolkit name is licensed; return zero exit status if it is, or nonzero if not.

-p name

Test if Daylight application program name is licensed; return zero exit status if it is, or nonzero if not.

-s name

Test if Daylight service is licensed; return zero exit status if name is an authorized service, or nonzero if not.

-t any
-p any
-s any

In the special case where name is "any", testlicense checks only that the license is valid and returns zero status if it is. It does not check for any particular program, toolkit, or service.

Return Value

Returns status zero if the license is found and is valid, or one if the license is invalid or can't be found. If there is a problem, a diagnostic message is printed. The '-v' option can then be used to debug the difficulty.

Examples

$DY_ROOT/bin/testlicense

Test for a valid license and print (on standard output) a list of licensed products.

$DY_ROOT/bin/testlicense -i

Print the machine's identifying information, e.g. on a Sun, it might print:

#hostname: myhost
cpu type: sun4u
cpu idno: 80abcdef
identity: ipv4,192.168.0.1
identity: cpu,sun4u,80abcdef
identity: lmhostid,80abcdef

$DY_ROOT/bin/testlicense -v

Print verbose debug information, e.g. on a machine with only a FLEXnet license file, it might print:

Version: 4.9
Requires support2 date of: 04/17/2006 or later
OPTIONS AVAILABLE

1. Trying DY_LICENSEDATA:
- Not found: /usr/local/daylight/dy_license.dat
2. Trying DY_LICENSEDIR:
- Not set
3. Trying well-known locations:
- Not found: /usr/local/daylight/dy_license.dat
- Not found: /daylight/dy_license.dat
- Not found: /tmp/dy_license.dat
4. Trying DY_DALI_SERVER:
- Not set
5. Trying DY_DALI_AUTHORITY:
- Not set
FLEXnet Summary:
FLEXnet License Search Path:
@myhost
/usr/local/daylight/daylight.lic
FLEXnet Licensed Features:

+ smiles_toolkit
- smarts_toolkit
+ thor_server 10

Files