Table of Contents * Previous Chapter * Next Chapter

Q11. FLEXlm utilities (lmutil - lmstat, etc.)

PC NOTE: On all platforms, the utilities can be invoked with the lmutil command: lmutil lmstat, lmutil lmremove, etc. On the PC, this is the only way to access the utilities. So where you see, for example, the lmstat command, read lmutil lmstat.

On a PC, you also have the option of using lmtools if it was included in your distribution package. lmtools is a Graphic Interface utility with the same functionality as lmutil.

Q11.1 How do I tell who's currently using a feature?

Use lmstat. This is a utility shipped to vendors and intended for distribution to end-users.

% lmstat -a -c license_file_path 

will list all the current information available from the server. Note that uncounted licenses are NOT reported by lmstat - only counted licenses.

Q11.2 How do I see historical usage of a feature?

Correct usage information can be obtained using FLEXadmin's reporting capability.

Q11.3 lmstat sometimes skips features, why?

This happens for 2 reasons:

• Uncounted features (number of licenses = 0) aren't shown by lmstat, since the number of users isn't relevant
• If an uncounted line has a daemon name of `none', there is a bug that lmstat will ignore subsequent counted features of the same name. To fix, simply change `none' to a valid daemon name.

Q11.4 How do I tell if I've typed in the license file correctly?

Use lmcksum (copy lmstat to lmcksum if you can't find lmcksum - See Q8.3). lmcksum -c `license-file'. If you have a v4.0+ license file, and the vendor has included `ck=nnn' on the FEATURE lines, lmcksum will simply report OK or BAD next to each FEATURE line. Otherwise, numbers are reported, and you can ask your supplier to run the same command on the original file, and compare numbers.

Q11.5 I'm getting `Cannot Connect' errors. How do I determine what's wrong?

Use the lmdiag utility. (If you can't find lmdiag, copy a v4.0+ version of lmstat to lmdiag, and you'll have it.) lmdiag will analyze the problem, and, if requested, determine if the problem is that the server is running on a different port than indicated in the license file.

lmdiag also prints out a description of the license file in easily understandable English.

In summary, lmdiag attempts a checkout of the feature, and if it fails, reports why.

Q11.6 lmremove doesn't seem to work: after freeing a license, it becomes checked out shortly after. Why?

That's because lmremove is not intended to free licenses. It has one purpose: when a client node crashes, the license is not freed immediately, and can sometimes take a full day to release the license. This is because when the node crashes the networking also fails.

If you free a license with lmremove for an active process, the application will detect this shortly, and re-checkout the license.

Q11.7 How do I prevent users at my site from being able to use lmdown?

Start the server with the lmgrd -x lmdown switch. This disables the lmdown command.

Q11.8 If I can't use lmdown, how do I shutdown the servers?

In UNIX, use kill, without a flag. DON'T use kill -9. If you use kill without a flag, the server is able to shutdown cleanly, the same, in fact, as if lmdown had been used.

In Windows, use the stop button under the FLEXlm License Manager in the Control Panel or lmutil lmdown in DOS. If all fails to shut down, Crtl-Alt-Del, END TASK(not recommended).

Q11.9 When I run lmdown on redundant servers, it doesn't seem to work. Why?

With redundant servers, lmdown returns immediately, but the servers, after having received the request, wait one full minute before actually shutting down. (This is in order to avoid a race condition where a second server would attempt to re-establish quorum with the server that shut down.) Be patient, wait the minute, and you'll see it works.