controls which plugins to load. These plugins ultimately define collectd's
behavior.
-The syntax of this config file is similar to the config file of the famos
+The syntax of this config file is similar to the config file of the famous
B<Apache Webserver>. Each line contains either a key-value-pair or a
section-start or -end. Empty lines and everything after the hash-symbol `#' is
ignored. Values are either string, enclosed in double-quotes,
B<false>. String containing of only alphanumeric characters and underscores do
not need to be quoted.
+Plugins are loaded in the order listed in this config file. It is a good idea
+to load any logging plugins first in order to catch messages from plugins
+during configuration.
+
=head1 GLOBAL OPTIONS
=over 4
=item B<SocketGroup> I<Group>
-If running as root change the group of the UNIX-socket after it has been
+If running as root change the group of the UNIX-socket after it has been
created. Defaults to B<collectd>.
=item B<SocketPerms> I<Permissions>
channels, respectively. This, of course, only makes much sense when collectd is
running in foreground- or non-daemon-mode.
+=item B<Timestamp> B<true>|B<false>
+
+Prefix all lines printed by the current time. Defaults to B<true>.
+
=back
=head2 Plugin C<mbmon>
=head2 Plugin C<nginx>
-This plugin collects the number of connections and requests handeled by the
+This plugin collects the number of connections and requests handled by the
C<nginx daemon> (speak: engineE<nbsp>X), a HTTP and mail server/proxy. It
queries the page provided by the C<ngx_http_stub_status_module> module, which
isn't compiled by default. Please refer to
=item B<LocalPort> I<Port>
Count the connections to a specific local port. This can be used to see how
-many connections are handeled by a specific daemon, e.E<nbsp>g. the mailserver.
+many connections are handled by a specific daemon, e.E<nbsp>g. the mailserver.
You have to specify the port in numeric form, so for the mailserver example
you'd need to set B<25>.
=item B<RemotePort> I<Port>
-Count the connections to a specific remote port. This is usefull to see how
+Count the connections to a specific remote port. This is useful to see how
much a remote service is used. This is most useful if you want to know how many
connections a local service has opened to remote services, e.E<nbsp>g. how many
connections a mail server or news server has to other mail or news servers, or
=item B<SocketGroup> I<Group>
-If running as root change the group of the UNIX-socket after it has been
+If running as root change the group of the UNIX-socket after it has been
created. Defaults to B<collectd>.
=item B<SocketPerms> I<Permissions>