Commit aa4da16f authored by 's avatar
Browse files

small update in mapi tutorial


git-svn-id: file:///home/svn/mapi/trunk@1295 8d5bb341-7cf1-0310-8cf6-ba355fef3186
parent 4cddb62c
No preview for this file type
...@@ -453,8 +453,9 @@ drvpath=/usr/local/share/mapi ...@@ -453,8 +453,9 @@ drvpath=/usr/local/share/mapi
libs=stdflib.so:extraflib.so libs=stdflib.so:extraflib.so
debug=2
dimapi_port=2233 dimapi_port=2233
syslog_level=1
logfile=
[driver] [driver]
device=eth0 device=eth0
...@@ -486,6 +487,21 @@ forward them to the local \textit{mapid} and return the answers and results from ...@@ -486,6 +487,21 @@ forward them to the local \textit{mapid} and return the answers and results from
The port number that \textit{mapicommd} uses to listen for incoming connections is defined in The port number that \textit{mapicommd} uses to listen for incoming connections is defined in
\textit{mapi.conf} located in the installation directory. \textit{mapi.conf} located in the installation directory.
Both mapi deamons, \textit{mapid} and \textit{mapicommd}, support loggism mechanism to files
and to syslog.
For logging to file, the filename is defined in \textit{mapi.conf} in the \texttt{logfile} field.
In order to log messages to syslog, mapid and/or mapicommd should be executed
with the flag -s (mapid -s and/or mapicommd -s).
Two different types of messages are sent to syslog, debug messages and
general information messages. \textit{mapi.conf} the syslog
level can be configured:
\begin{itemize}
\item \textbf{syslog\_level=0}: Log only general information and not debugging messages.
\item \textbf{syslog\_level=1}: Log general information plus debugging information. Debug messages are printed to stdout and syslog.
\item \textbf{syslog\_level=2}: Log general information plus debugging information. Debug messages are printed only to syslog.
\end{itemize}
The default level is 2.
\subsection{Compiling new MAPI applications} \subsection{Compiling new MAPI applications}
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment