User guide

Chapter 4 - Selecting License Server Machines

Remote Mounted Disks

40 FLEXnet Licensing End User Guide

Disk Space

The only output files created by the license server systems are the debug and report log files.

The report log files are used to generate accurate usage reports by FLEXnet Manager. If you

have a lot of license activity, these log files grow very large. You need to consider where to put

these files and how often to rotate and archive them. The license administrator has the option

to suppress log file output if disk space is at a premium.

It is recommended that the log files are local files on the server machine(s) to avoid networking

dependencies.

See Also

• “Setting the Path with an Environment Variable”

• “Starting the License Server Manager on UNIX Platforms”

• Appendix F, “The Report Log File”

• Appendix G, “The Debug Log File”

Memory

The FLEXnet license server system uses little memory. On SunOS, lmgrd uses

approximately2 MB and the vendor daemons use approximately 2 MB each, although memory

usage increases in the vendor daemon with the size of the license file, size of the options file,

and the number of concurrent users.

Network Bandwidth

FLEXnet Licensing sends relatively small amounts of data across the network. Each

transaction, such as a checkout or checkin, is typically satisfied with less than 1 KB of data

transferred. This means that FLEXnet Licensing can be effectively run over slow networks

(such as dial-up SLIP lines) for small numbers of clients.

For a large number of FLEXenabled applications (hundreds), each of which exchange heartbeat

messages with the vendor daemon, the network bandwidth used may start to become

significant. In this case, run the FLEXenabled application and server on the same local area

network, which may require splitting licenses between two files for two servers. Users can use

a license-file list in the

LM_LICENSE_FILE environment variable to have effective access to

both servers.