with your software vendors for the newest available versions of their vendor
daemons.
■
In pre v 5.1 vendor daemons, rereads, and shutdowns could possibly
introduce corruption, particularly if the server is busy. With these older
vendor daemons, the best policy is to issue reread or shutdown when no
licenses are checked out, if possible.
■
Issuing an lmdown command while the server is shutting down can cause
corruption.
■
Don't move, copy, or edit the report log file while the server is running.
■
Never configure more than one license server to write to the same report
log file. In the case of a redundant server, each vendor daemon must write
to a distinct file, preferably one which is local to the server machine. Even
if the report log is not corrupted, SAMreport-Lite will not run a report using
a report log that has been written by a vendor daemon running on more
than one license server machine.
■
Never configure different vendor daemons to write to the same report log
file. Even if the report log is not corrupted, SAMreport-Lite will not run a
report using a report log that has been written by more than one vendor
daemon.
■
Do not use lmswitchr or -switchlog to switch the report log to an existing
report log file. Switch to a file with a new name.
■
Never hand-edit a report log or combine report logs together into the same
file.
■
If you change a server host name, make sure you stop the license manager
and create a new report log when the name change is complete.
28 | Chapter 6 Enabling and Managing Report Logs
