The sm_getinfo utility, which is supported on CentOS, and Linux, creates four types of files in the installation directory area from which it is invoked. The files are shown described in Files created by the sm_getinfo utility.

Table 1. Files created by the sm_getinfo utility



Files in BASEDIR/smarts/local/logs directory



A compressed tar archive in which the sm_getinfo utility stores a server ‘s log files, repository files, core files (CentOS, Linux) , user-modified files (using sm_edit), user-introduced files, and system environment information. The actual content of the tar archive depends on the user-specified options on the sm_getinfo invocation command line.

The name of the tar archive includes the date when the tar archive was created.


A text file that lists all of the files that the sm_getinfo utility includes in the tar archive.

Files in BASEDIR/smarts/local/logs/smgetinfo_files directory



Example of other files in smgetinfo_files:TTP-Installed-versions.log.26Mar2012-020005

A log file in which the sm_getinfo utility writes information about a server’s log file or repository file that is larger than 700 megabytes (MB). The sm_getinfo utility does not include any log or repository file in a server’s tar archive that exceeds 700 MB.

In addition, sm_getinfo writes system information to the log file.

The name of the log file includes the date when the log file was created.



The -k or --smconfigscan command invokes the Configuration Scanner tool, and generates the Final_getinfo-<timestamp>.tar, along with other Configuration Scanner tool-related files.


If the sm_getinfo utility is run without the -k or --smconfigscan command, a getinfo-<timestamp>.tar output file will be generated without Final_ appended to the output. This implies that you will be running the sm_getinfo tool as usual.