STW TC1 - Page 225

7 Teleservice Application Framework
User Manual 225/374
7.3.6.4 Handle Logger File
Header file: "DL_LogFile_handler.h"
This header provides utility functions to use the logger daemon to handle logger files.
7.3.6.4.1 ylogd_request_data_logger_file
Function Description
sint32 ylogd_request_data_logger_file (const T_DBUS_Util *const opt_DBusInstance, const
charn * const opcn_DataLoggerName, charn * const opcn_DataLoggerPath, const uint16
ou16_BufferSize)
The function requests the datalogger file opcn_DataLoggerName. If the logger file exists, the path to a copy
(tmp file) will be responded via the variable opcn_DataLoggerPath. The maximal length of the path to the
datalogger copy is defined via ou16_BufferSize.
Information Flow
Input Information
Parameter
Range
Description
opt_DBusInstance
T_DBUS_Util
holds all D-Bus information
opcn_DataLoggerName
maximum
MAX_DL_NAME_LENGTH
pointer to the name of the datalogger
ou16_BufferSize
minimum
MAX_DL_BASEFOLDER_LENGTH
maximum buffer size of datalogger path
Structure T_DBUS_Util
typedef struct
{
DBusConnection* pt_dbus_conn; // D-BUS connection instance
charn acn_myNameString[128]; // Name of the application, Don't use any
special
// characters, white spaces or new lines!
charn acn_myVersion[128]; // Additional value (for HELLO) signal (opt.)
charn acn_myStatus[128]; // Additional value (for HELLO) signal (opt.)
charn acn_myAddInfo[512]; // Additional value (for HELLO) signal (opt.)
sint32 s32_myTriginterval; // Time interval when the ysysd
// expects to be triggered
charn acn_myCMDOnWatchdog[2048]; // Bash cmd that must be executed
// by the ysysd in case no
// trigger signal occurred in time.
} T_DBUS_Util;