cd /usr/local; tar xvzfo /where-you-saved-it/hlserver-f13-v2.*.tgz

HLServer versions up to v2.05 use /usr/tmp to save a PID file when running. If /usr/tmp doesn't exist, then HLServer may start, but will exit soon after. Creating a symbolic link from /tmp to /usr/tmp will fix this problem for those earlier releases.

The following files make up the Linux license server installation:

hlserver 

This is the server application. It need not be run with any special privileges unless the PORT used is under 1027.

hlserver.conf 

The contents of this file, explained in detail in Server Config, controls the behavior of the server.

hlserver.log 

This is a series of date stamped log messages from the server showing, amongst other things, who is grabbing which licenses.

setup.redhat 

This is a RedHat/Fedora script that can be used to start the server on 'init' based boots, and stop it on shutdown. Installation instructions are in the file.

setup.systemd 

This can be used to start the server on 'systemd' based boots. Installation instructions are in the file.

setup.debian 

Start/stop script for Debian/Ubuntu based systems. Installation instructions are in the file.

hlmanager 

This is the manager application. See The Manager chapter for details.

keys.txt 

This file holds the floating license keys. Was called .keys in earlier versions.

[edit] Setup v2

To complete the initial setup, login as root and run hlserver from the command line ...

 /usr/local/hlserver/hlserver

You should see a message like the following ...

 hlserver: Started hlserver v2.04 2017/07/11 17:12:52 on port 11668
 hlserver: Using files and keys from '/usr/local/hlserver'
 hlserver: Running in foreground.
 hlserver: We recommend using one of the setup scripts provided to run hlserver as a background daemon.
 hlserver: Now run hlmanager to complete the installation.

Next, from another command shell window, login as a normal user and run hlmanager ...

 /usr/local/hlserver/hlmanager

You should see something like this ...

Trying architec@localhost ... Connected ... Fetching ...
Server v2.00 localhost up 00:00

  Your login has been added automatically to
  the hlserver.conf file for Manager access.
  If you want to add Manager access for other
  users, you will need to edit that file on
  the server.

----------------------------------------------

  No valid floating licenses found. Please
  email the following code to your vendor so
  new license keys can be generated.

  6JZ5 2PLM 2EB3 GM4X 3W53 CEL1 PAX8 MNKB

  Copy of above code: '/tmp/hlmanager-code.txt'

  If you've already received your license keys,
  now use the "add" command to append one at
  a time to the keys file on the server.

So email that code to your vendor to get your license keys.

In the meantime, kill the foreground 'hlserver' process, then follow the instructions in whichever 'setup.*' script is appropriate for your system to run hlserver as a background daemon.

Once you have some keys, re-run hlmanager and use the 'add' command to append them to the keys file on the server. You should see something like this once the keys have been added.

> add
Enter key string below ...
FMWM 6N8S 0BPS 4FXP K4GL W7H7 6JFY R8B4 8NDB JP3A
Sending key to server ...
Updating status ...
Server v2.00 localhost up 00:05
<--------- Licenses ---------->
Name        Status    Free Used
uvlayoutv2  29 days      4    0

Users should now be able to access the license server from others systems on the local network.

[edit] Setup v1

You will need root access on the server host to do this; read the appropriate script file for full installation instructions.

Copy sample-hlserver.conf into hlserver.conf and edit to suit your network setup. You should at least change the IP range for the lan group.

Run 'hlserver' from the command line when first installed. You'll get a "License not found" type error, and 5 rows of hex numbers; email these to your vendor to get your license strings.