\section{Logging}

\subsection{Opening log files}

\begin{verbatim}
# log.open_file = "log name", "file path"

log.open_file = "rtorrent.log", (cat,/tmp/rtorrent.log.,(system.pid))
\end{verbatim}

A newly opened log file is not connected to any logging events.

Some control over formatting will be provided at a later date.


\subsection{Adding outputs to events}

\begin{verbatim}
# log.add_output = "logging event", "log name"

log.add_output = "errors", "rtorrent.log"
log.add_output = "events", "rtorrent.log"

log.add_output = "dht_all", "tracker.log"
log.add_output = "tracker_events", "tracker.log"
log.add_output = "tracker_requests", "tracker.log"
\end{verbatim}

Each log handle can be added to multiple different logging events.


\subsection{Logging events}

\begin{verbatim}
"errors"
"events"
"debug_trace"
\end{verbatim}

The above events are not cascading, so add both ``errors'' and
``events'' to an output to receive both.

High-volume sub-group events such as ``tracker\_debug'' are not part
of ``debug\_trace''.

\begin{verbatim}
"connection_*"
"dht_*"
"peer_*"
"rpc_*"
"storage_*"
"thread_*"
"tracker_*"
"torrent_*"
\end{verbatim}

All sub-groups have events from ``critical'' to ``debug'' defined.