DEBUGLOG

Specifies a location for the debug log output from the vendor daemon associated with this options file. Preceding the debug_log_path with a + character appends logging entries; otherwise, the file is overwritten each time the daemon is started. Note that this affects output from only the vendor daemon associated with this options file. The debug log output of the license server manager and any other vendor daemons in the same license file is not captured in this file. Generating debug logs with DEBUGLOG keyword is better alternative than lmgrd command line option -l when debug log is only required for the vendor daemon. One of the advantage is that server detaches itself from previous debug log after server has been linked to new debug log through lmswitch or with server reread (option file DEBUGLOG keyword edited to new debug log).

DEBUGLOG [+]debug_log_path [OBF_ADDMARK] [AUTO_ROLLOVER size]

On Windows, path names which include spaces have to be enclosed in double quotes. If lmgrd is started as a service, the debug log file is by default generated in the path specified in the options file. It is best practice to set the location of debug_log_path 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. The OBF_ADDMARK enables the affixing of obfuscation markers (OBF_STRT: username :END_OBF) to username in debug log. The AUTO_ROLLOVER option enables the auto rollover of debug log file, which automatically performs the rollover functionality of debug log file when the debug log file size crosses the specified value. The default value would be 512MB. The automatic rollover will always be performed at midnight.