Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ license.dat(4M) — DG/UX R4.11

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

lmgrd(1M)

admuserlicense(1M)

admlicense(1M)

usermond(1M)



license.dat(4M)                  DG/UX R4.11                 license.dat(4M)


NAME
       license.dat - license configuration file for FLEXlm licensed
       applications

SYNOPSIS
       /etc/license.dat

DESCRIPTION
       The format of the license file is dictated by FLEXlm, a third party
       licensing package.  The license file contains three types of lines,
       SERVER, DAEMON, and FEATURE lines.  A license file consists of any
       number of SERVER lines followed by any number of DAEMON lines,
       followed by one or more FEATURE lines.  The purpose of the SERVER
       line is to describe a FLEXlm server.  From the FLEXlm perspective, a
       server is a machine running both the license daemon and the vendor
       daemon.  DAEMON lines tell the license daemon which vendor daemons to
       start.  A FEATURE line describes the license for a feature or
       application.  An example of a license file is:

         SERVER fireball c021757 744

         DAEMON dguxuserd /usr/sbin/dguxuserd

         FEATURE dg_test_admin dguxuserd 1.00 1-jan-98 01
              EB55190F7FE2AB4549A1   "cust id 00001234" ANY

         FEATURE dgtest dguxuserd 1.00 1-jun-99 16 AC45198F7E12AB401746
              "cust id   00001234" ANY

       This license file would allow 16 copies of dgtest, and 1 copy of
       dg_test_admin to be run anywhere on a network that could access the
       server fireball.  The license daemon, lmgrd(1M), will start the
       vendor daemon dguxuserd on fireball by executing /usr/sbin/dguxuserd.
       The license file is read by either lmgrd(1M) for networked licenses,
       or by certain Data General applications which restrict use based on a
       license defined in the license file.  The contents of each line in a
       license file is discussed below.  All data in the license file is
       case sensitive, unless otherwise indicated.


   Server line
       SERVER hostname id tcp-port-number

   where:
       hostname
              The string returned by the UNIX hostname(1M) command.  This
              field can be modified by the end user without corrupting the
              license file.  The hostname should be something that would be
              returned by gethostbyname(3N) and the host on which the
              license file resides must have a route to the given host.

       id     The string returned by the lmhostid(1M) command or the string
              "any" to allow the use of any server (Case insensitive).

       tcp-port-number
              The TCP port number to use.  This is important because more
              than one license daemon, lmgrd(1M), may be running on a single
              machine.  Changing the port number when necessary should allow
              more than one license daemon to run on the same machine
              without interfering with each other.  The default port number
              is 744 and is reserved for FLEXlm in /etc/services.  The tcp-
              port-number field is one of only four that can be changed by
              the end user.

   Vendor daemon line
       DAEMON daemon-name path [options_file]

   where:
       daemon-name
              The name of the vendor daemon used to serve features in the
              file.

       path   The path name to the executable code for this daemon.  This
              field can be modified by the end user without corrupting the
              license file.

       optionsfile
              The path name of the end-user specified options file for this
              daemon.  This field can be modified by the end user without
              corrupting the license file.

   Feature line
       FEATURE name daemon version exp_date #users code "vendor_string"
              [hostid]

   where:
       name   The name given to the feature. "SERVER" and "DAEMON" are
              illegal.

       daemon The daemon-name from a DAEMON line. The specified daemon
              serves this feature.

       version
              The latest (highest-numbered) version of this feature that is
              supported. (3 decimal places. 1.100 for example).

       expdate
              The expiration date in the format:

              dd-mmm-yyyy, (for example, 22-mar-1996).

              Note that if you do not want the feature to expire, select an
              expiration date with the year as 0 (any day-any month-0).
              (Case insensitive).

       #users The number of users licensed to use this feature.

       code   The encryption code for this feature line. (Case insensitive).
              The encryption code is encrypted with the data from the
              license file.  Therefore, if a user changes the license file,
              the file may be corrupt.

       vendor-string
              The vendor-defined string, enclosed in double quotes.  This
              string can contain any 64 characters except a double quote
              (white space will be ignored in the vendor-defined string).

       hostid The string returned by lmhostid(1M). Use if this feature is to
              be bound to a particular host, whether its use is counted or
              not. The string "ANY" can be used instead of a particular
              hostid. (Case insensitive).

       A license file is an encrypted file.  The encryption code for each
       feature contains information including the hostids on SERVER lines,
       the vendor daemon names from DAEMON lines, and all of the information
       in it's own FEATURE line.  There are only four items in a license
       file that can be modified without corrupting the encryption code for
       a particular feature.  These four items are:

         ·    server hostnames on SERVER lines

         ·    TCP port numbers on SERVER lines

         ·    the daemon path on DAEMON lines

         ·    the options file path on DAEMON lines.

       Note that there are no fields in a FEATURE line which can be modified
       without making the encryption code invalid and thus corrupting the
       license file.  If a FEATURE line has an invalid encryption code, the
       license for that feature will be unavailable.

       Any amount of white space of any type can separate the components of
       the line, and the line can be entered via any text editor.  Therefore
       we can distribute licenses data via fax or telephone.

       Comment lines are allowed and may begin with "#".  There is no
       restriction on the number of license files that can reside on a
       single machine.  If the license file is to be used with its full
       functionality (i.e. read by lmgrd(1M) which will start the vendor
       daemon(s), client applications checking out licenses using FLEXlm
       library routines), then a copy of lmgrd(1M) will have to be running
       for each license file.

EXAMPLE
       Here is an example of a license file.


       SERVER fireball ANY 744

       DAEMON dguxuserd /usr/sbin/dguxuserd

       FEATURE dgux dguxuserd 1.000 06-jun-0000 16 EA4F64AD610C5F330C91
              "cust id 11112222" ANY

       FEATURE nwaviion dguxuserd 1.0 10-nov-1996 2 1BF4700169FB78AE692E
              "cust id 00001234" ANY

       This example illustrates the license file for a single vendor with
       two features.  The license file will allow 16 users of the feature
       dgux and 2 users of the feature nwaviion to execute on any machine.
       The license for dgux will never expire whereas the license for
       nwaviion expires on November 10, 1996.

FILES
       /etc/license.dat

SEE ALSO
       lmgrd(1M), admuserlicense(1M), admlicense(1M), usermond(1M).


Licensed material--property of copyright holder(s)

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026