Launcher log file
When it is started, the Launcher service (or daemon) begins to write to the LauncherLog_timestamp_hostname.log file. The Launcher Admin process starts Launcher processes to execute launcher systems. Launcher processes write trace messages to the system_name_timestamp_hostname.log file. The LauncherLog_timestamp_hostname.log file contains session-related logging information, such as initialization settings from the Launcher Administration. The system_name_timestamp_hostname.log file contains system processing information such as system command lines, system commands from the Management Console, map execution status, I/O related messages, system status, and any exceptions.
When the system_name_timestamp_hostname.log file reaches a maximum size, the Launcher process closes it, appends an index number to log file name (system_name_timestamp_hostname_index.log), and begins logging to a new file. You can specify the maximum size of the system_name_timestamp_hostname.log file size on the CircularLogSize option in the config.yaml configuration file. The default maximum size is 100 MB, and the minimum size is 10 MB.
You also can specify the maximum number of system_name_timestamp_hostname.log files to keep before the oldest log file is deleted. The CircularLogFileNum option in the config.yaml file controls the maximum number of log files. The minimum is two log files, and the default maximum is five log files.
The initial LauncherLog_timestamp_hostname.log file that is created at Launcher service startup is never deleted. When the Launcher service restarts, it creates a log file with a new timestamp.