🎉 We're happy to announce new public releases 🎉

  • TriCore v6.2r2 Inspector v1.0r8 - An automated method for identifying toolset issues in compiled output code
  • VX-toolset for Arm - v8.0r1 - A certified compiler toolset for safety critical embedded software development on Arm cores
Contact us to get access

Categories

FLEXlm
FLEXlm: License handling after client failure 19-Sep-2025
If the client dies, the server frees the license, unless the client's whole system crashes. Assuming communication is TCP, the license is automatically freed immediately. If communications are UDP, then the license is freed after the UDP timeout, which is set by each vendor, but defaults t...
FLEXlm: Working with NIS and DNS 19-Sep-2025
FLEXlm works with NIS and DNS. However, some sites have broken NIS or DNS, which can cause FLEXlm to fail. In version 5 of FLEXlm, NIS and DNS can be avoided to solve this problem. In particular, sometimes DNS is configured for a server that is not currently available (for example, a dial-...
FLEXlm: Working with subnets, fully-qualified names, multiple domains, etc. 19-Sep-2025
FLEXlm works with subnets, fully-qualified names, multiple domains, etc. Although this behavior was improved in v3.0, and v6.0, when a license server and a client are located in different domains, fully-qualified host names have to be used. A fully-qualified hostname is of the form: machin...
FLEXlm: Is the old license file still valid if a new copy of a product is received from a vendor, and it uses a new version of FLEXlm? 02-Dec-2024
Yes. Older FLEXlm license files are always valid with newer versions of FLEXlm. More resources FLEXlm License Management System - Overview FLEXlm Downloads
FLEXlm: Format of the new license file from the same vendor is different from the old one 02-Dec-2024
As of v3.0, FLEXlm has an optional new format for license files. FLEXlm products always understand older versions; therefore, the pre-v3.0 files are understood by every FLEXlm version. However, your old applications (pre-FLEXlm v3.0) will not be able to use the new license file. See also S...
FLEXlm: Compatibility between products from different companies running on various FLEXlm version levels 02-Dec-2024
If you are not combining license files from different vendors, the simplest thing to do is make sure you use the tools (especially lmgrd ) that are shipped by each vendor. As lmgrd always correctly supports older versions of vendor daemons and applications, it's always safe to use the late...
FLEXlm: Does FLEXlm licensing impose a heavy load on the network? 02-Dec-2024
No, but partly this depends on the application and end-user's usage. A typical checkout request requires five messages and responses between client and server, and each message is 150 bytes. When a server is not receiving requests, it requires virtually no CPU time. When an application, or...
FLEXlm: Improve performance when using FLEXlm over a wide-area network 28-Nov-2024
To improve performance, FLEXlm network traffic should be minimized. With the most common uses of FLEXlm, traffic is negligible. In particular, checkout, check-in, and heartbeats use very little networking traffic. There are two items, however, which can send considerably more data and shou...
FLEXlm: License server does not start on Windows 7 28-Nov-2024
On Windows 7, the license server does not start when configured to run as a service. You may receive one of the following error messages: The service did not respond to the start or control request in a timely fashion. The FLEXlm License manager does not respond in a timely manner. Server ...
FLEXlm: Is the FLEXlm 'display' the same as an X-Display? 28-Nov-2024
Not by default. The default FLEXlm display is what is returned by the ttyname() function call (or the tty command), and is usually something like /dev/ttyp4 . However, the application developer can change this default to the X-Display. More resources FLEXlm License Management System - Over...
FLEXlm: Error message on GLIBC_2.0 when starting lmgrd on Linux 27-Nov-2024
On some systems, when starting lmgrd on Linux, it displays the following error message: relocation error: ./lmgrd: symbol errno, version GLIBC_2.0 not defined in file lib.so.6 with link time reference Possible solution Prepend LD_ASSUME_KERNEL=2.4 to the lmgrd startup command. For example:...
FLEXlm: Determine when to combine license files 27-Nov-2024
Many system administrators, especially for larger sites, prefer to combine license files to ease the administration of FLEXlm licenses. It is purely a matter of preference. More resources FLEXlm License Management System - Overview FLEXlm Downloads 
FLEXlm: Do I have to combine the FLEXlm license files received from 2 different companies? 27-Nov-2024
You do not have to combine license files. Each license file that has any counted lines (the number of licenses field is 0) requires a server. It is perfectly OK to have any number of separate license files, with different lmgrd server processes supporting each file. Moreover, since lmgrd i...
FLEXlm: Does FLEXlm require root permissions? 27-Nov-2024
No. There is no part of FLEXlm, lmgrd , vendor daemon, or application, that requires root permissions. It is strongly recommended that you do not run the license server (lmgrd) as root, since root processes can introduce security risks. If lmgrd must be started from the root user (for exam...
FLEXlm:Determine if a port is already in use 27-Nov-2024
99.44% of the time, if it is in use, it is because lmgrd is already running on the port - or was recently killed, and the port is not freed yet. Assuming this is not the case, then use telnet host port - if it displays can't connect , it is a free port. More resources FLEXlm License Manage...
FLEXlm: Is it OK to run lmgrd as 'root' (Unix only)? 27-Nov-2024
It is not prudent to run any command, particularly a daemon, as root on Unix, as it may pose a security risk to the Operating System. Therefore, it is recommended that lmgrd is run as a non-privileged user (not 'root'). If you are starting lmgrd from a boot script, we recommend that you us...