- <p>Specifies the location of a <span class="fixedwidth">log4cpp</span> which
- overrides the <span class="fixedwidth">[general]</span> log parameters for
- SHIRE events. Default logging settings should
- suffice. The <span class="fixedwidth">syslog</span> daemon must accept
- <span class="fixedwidth">UDP:514</span> messages, and on Linux,
- <span class="fixedwidth">SYSLOGD_OPTIONS</span> must include <span class="fixedwidth">-r</span> to
- <span class="fixedwidth">enable logging from remote machines.</span> The
- logging levels are defined in the logger
- configuration. The configuration format is similar to
- that of the <a
- href="http://jakarta.apache.org/log4j/docs/
- documentation.html">Log4j</a> package's format.</p>
+ <p>Specifies the location of the <span class="fixedwidth">log4cpp</span>
+ configuration file for most Shibboleth events. This
+ element may also be optionally specified for each of
+ the components individually. Default logging settings (using local log files)
+ should suffice. If using a remote syslogd instead, the <span class="fixedwidth">syslog</span>
+ daemon must accept <span class="fixedwidth">UDP:514</span> messages, and on Linux,
+ <span class="fixedwidth">SYSLOGD_OPTIONS</span> must include <span class="fixedwidth">-r</span>
+ to <span class="fixedwidth">enable logging from remote machines.</span> The
+ logging level is also defined in the logger configuration.
+ The configuration format and log levels are similar to that of the
+ <a href="http://jakarta.apache.org/log4j/docs/documentation.html">Log4j</a> package's
+ property format.</p>