User's Manual

hp StorageWorks File System Extender User Guide 225
The following table represents the values the HSM_DEBUG_LEVEL variable can take, their corresponding
levels, and their descriptions.
Example
HSM_DEBUG_FILE
The following table represents the values the HSM_DEBUG_FILE variable can take and their descriptions.
It is recommended to use the value . (dot), which results in each process producing its own trace file. The
other two cases ("" and FileName) are for special purposes only and should not be used unless required
by HP support personnel.
Example
Debugs can occupy a lot of disk space when troubleshooting an unpredictable problem.
Option value Debugging level Description
L 1 — Low Very little trace information will be
logged in files, producing less debug
overhead and small debug files.
N 2 — Normal The usual level of detail in debug
trace files.
A 3 — API Trace third-party API calls (CORBA,
Firebird…).
D 4 — Detail Trace all process details, which can
produce a lot of debug output.
HSM_DEBUG_LEVEL=A
Option value Description
""
(empty string or variable commented out;
default value)
Debugs will be written to the standard output stdout.
.
(dot)
Debugs will be written to files (one per FSE process) in a directory,
depending on the platform:
Linux specific
/var/opt/fse/log/debug
Windows specific
%InstallPath%\var\log\debug
The value of %InstallPath% depends on the choice made in the FSE
installation process. It defaults to C:\Program
Files\Hewlett-Packard\FSE.
FileName All FSE processes will print their trace data into the file named
FileName.
Linux specific
The location of the file is /var/opt/fse/log/debug/FileName.
Windows specific
The location of the file is
%InstallPath%\var\log\debug\FileName.
HSM_DEBUG_FILE=.