lmswitch

The lmswitch utility when used without rollover argument switches the debug log file written by a particular vendor daemon by closing the existing debug log for that vendor daemon and starting a new debug log for that vendor daemon with a new file name. It also starts a new debug log file written by that vendor daemon if one does not already exist.

The lmswitch utility when used with rollover argument rolls over the debug log by moving the existing debug log content to a new file, then starting the new debug log with original debug log file name. If the file name is not specified, debug log would be rolled-over to a file with a predefined file name format.

Note:The lmswitch utility always writes in a new debug log file. If the file already existed, an error will be shown.

Usage

lmswitch [-c license_file_list] vendor new_debug_log -rollover

where:

lmswitch Argument Usage
Argument	Description
-c license_file_list	Use the specified license files.
vendor	Vendor daemon in this license file.
new_debug_log	Path to new debug log file.
-rollover	Rolls over the debug log by moving the existing debug log content to a new file, then starting the new debug log with original debug log file name. If the file name is not specified, debug log would be rolled-over to a file with name format as <vendor daemon name><hostname><date>_T<time>.log.

By default, debug log output from the license server and all vendor daemons started by the server get written into the same debug file. lmswitch allows companies to keep separate log files for different vendor daemons and control the size of their debug log file.

If debug log output is not already directed to a separate file for this vendor daemon, lmswitch tells the vendor daemon to start writing its debug log output to a file, new_debug_log. If this vendor daemon is already writing to its own debug log, lmswitch tells the vendor daemon to close its current debug log file and start writing its debug log output to new_debug_log.

Note:The effect of lmswitch continues only until the vendor daemon is shut down or its options file is reread via lmreread. When the vendor daemon is restarted or its options file is reread, it looks for a DEBUGLOG line in the options file to determine whether or not to write its debug log output into its own file and, if so, what file to write. It is best practice to set the location of new_debug_log to a ProgramData sub-folder, since this location has user-write permission by default, which is needed when the license server runs as a service with LocalService permission.

Note:The lmswitchsecure utility must be utilized in order to enable the encrypted communication with the vendor daemon.