Managing Report Logs

Remember that you can produce a report from multiple report logs as long as each report log is written by a single vendor daemon running on a single machine. (Vendor daemons running on more than one redundant server must write to their own report logs.) Therefore, to keep the size of report logs manageable, you should regularly close out a current report log and begin to write to a new one. This process is known as rotating report logs. A recommended method for rotating report logs is provided later in this section.

You may want to automate the process of managing each license server's report logs. The following steps can be performed on a regular basis:

  1. Rotate a report log. To avoid corruption in your report logs, we recommend that you rotate your logs with the FLEXlm utility, lmswitchr (found in the lmtools interface).
  2. Update the vendor daemon's options file(s).
  3. Move the older report log to a designated location.
  4. Archive (and probably compress) a report log when it is no longer needed to run reports.

You must rotate a report log at the following times:

NoteYou can corrupt a report log by rotating it incorrectly. A report log must begin with a header that is written by the vendor daemon. Without this header, the report log is corrupted. The data in the report log is unusable and unsalvagable from the start of the report log until the first time in that report log that the license server is restarted.

The report log will have no header and will be corrupted if you manually copy an active report log to a new file name, delete the original active report log, and keep the vendor daemon writing to the original active report log file name.