Command Reference Guide

2.14 NAME 95
– If string other than "." is specified, it will be considered as a file name
for single FSE debug file, where all running FSE processes will write
their debugging information into.
In both cases the log file(s) will be put in the /var/opt/fse/log/debug direc-
tory.
This argument may only be used together with the SysDbgLevel argument.
If it is not used, each FSE process writes the debugging data to its corre-
sponding standard output stream (stdout).
• SysDbgFlags
A string composed of one or more (different) uppercase letters from the set
{"I", "N", "C", "T", "E", "V"}. This argument specifies in detail which
events in the running FSE processes are logged and defines the form of the
debug output in an FSE debug file. The letters have the following meaning:
– I ... Function in & out. Specify that entries and exits from functions
should be logged. This choice results in large amounts of debugging
information.
– N ... No–header form. Specify that no FSE debug file header is
printed.
– C ... Compact–header form. Specify that a compact FSE debug file
header instead of the full one is printed.
– T ... Exception throw. Specify that all events that cause an exception
throw should be logged.
– E ... Error occurrence. Specify that major errors which occur in the
FSE processes should be logged. Note that such errors are normally
only logged in the FSE error log file.
– V ... Verbose third–party debugging.
This argument may only be used together with the SysDbgFile argument.
If it is not used, no events are logged – only the FSE debug file header is
printed.
• SysDbgHSMFS
HSM file system debugging flags, specified by a positive hexadecimal inte-
ger number of the form 0xNNNNNNNN. These flags enable logging of the
File System Extender 3.2 Command Line Reference