Specifications

MOS Gateway Configuration File
81
The <logging> Group
<logging>
<directory>DIRECTORY_GOES_HERE</directory>
<maxFileCount> COUNT_GOES_HERE</maxFileCount>
<maxFileBytes> SIZE_GOES_HERE</maxFileCount>
<winDebugTrace>WINDEBUGTRACE_YESNO</winDebugTrace>
<socket>SOCKET_ONOFF</socket>
</logging>
The DIRECTORY_GOES_HERE should be changed to the directory in
which the MOS Gateway will save its log files.
The COUNT_GOES_HERE should be changed to the maximum number of
log files that the MOS Gateway will create before recycling them.
The SIZE_GOES_HERE should be changed to the maximum size each
log file can be, such as 1000000 (which equals about 1MB).
n
Specify values that will not overflow the available storage space. For
instance, if you set the maximum file count to 100 and the maximum file
size to 1000000 bytes, ensure that you have 100 MB of free space in the
logging directory.
The WINDEBUGTRACE_YESNO should be changed to YES if logging
should be sent to the global Win32 debug subsystem. This is useful if the
system has a Win32 debugger that can display statements in real time.
Socket logging can
affect performance, so
it should not be left on
all the time.
The SOCKET_ONOFF should be changed to ON if socket level log files are
required. Socket logging logs all incoming socket messages in network
byte order. The logs are used when a device is sending data that the MOS
Gateway cannot handle. Each connected device and port has its own socket
log, created in the logging directory, as indicated by the MOS
configuration file.
The file name of the log is created using the mosID of the device to which
MOS Gateway is connected and a string that represents the connection
type, according to the following format:
[mosID][space][LM|UR][space][NCSInit|MOSInit].bin
• LM means "Media Object Metadata port"