Command Reference Guide

2.14 NAME 94
administrator. Usage of this option overrides current debugging settings in
FSE tracing configuration file (see section FILES), but its effect is limited
to the period of time until FSE processes are stopped with the fse command
(current FSE session). After the processes are restarted, the settings in FSE
tracing configuration file apply.
Note:
Usage of this option has no effect on debugging of the currently running
Back End Agents. However, it has an effect on debugging of the Back
End Agents which will be started later in current FSE session.
• SysDbgLevel
Debugging level identifier whose value can be one of the following upper-
case letters: L, N, A or D. The letters have the following meaning:
– L ... Low debugging level. Specify that only the most important in-
formation should be logged in FSE debug files. This level of logging
causes practically no debugging overhead and produces small debug
files.
– N ... Normal debugging level. Specify that information which is most
frequently used for debugging should be logged.
– A ... API debugging level. Specify that besides the most frequently
used debugging information all API calls to third–party components
(omniORB/CORBA, Firebird SuperServer) of the FSE system should
be logged.
– D ... Detailed debugging level. Specify that all details of the FSE
processes should be logged. This level of logging causes a noticeable
debugging overhead and produces a lot of debug output. This argu-
ment may only be used together with the – –enable–dbg option.
• SysDbgFile
An alphanumeric string which specifies where the debugging information is
recorded. This argument can be used in two ways:
– If "." character (a dot) is specified, FSE processes will write their
debugging data in corresponding files with file names of the form
<programName>_<processID>.log. Each generated log file will
correspond to a single running FSE process;
File System Extender 3.2 Command Line Reference