summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: a545d8f)
raw | patch | inline | side by side (parent: a545d8f)
author | Sebastian Harl <sh@tokkee.org> | |
Tue, 22 Feb 2011 09:17:46 +0000 (10:17 +0100) | ||
committer | Sebastian Harl <sh@tokkee.org> | |
Tue, 22 Feb 2011 09:17:46 +0000 (10:17 +0100) |
src/collectd.conf.pod | patch | blob | history |
diff --git a/src/collectd.conf.pod b/src/collectd.conf.pod
index 48a1e73c37cc7af1101de50b2d782f571c24eabf..13b85f3c1f2d4f0613c5845fd0c628d8fab7e931 100644 (file)
--- a/src/collectd.conf.pod
+++ b/src/collectd.conf.pod
=item B<User> I<Username>
Username to use when connecting to the database. The user does not have to be
-granted any privileges (which is synonym to granting the C<USAGE> privilege).
-Any existing MySQL user will do.
+granted any privileges (which is synonym to granting the C<USAGE> privilege),
+unless you want to collectd replication statistics (see B<MasterStats> and
+B<SlaveStats> below). In this case, the user needs the C<REPLICATION CLIENT>
+(or C<SUPER>) privileges. Else, any existing MySQL user will do.
=item B<Password> I<Password>
=item B<SlaveStats> I<true|false>
-Enable the collection of master / slave statistics in a replication setup.
+Enable the collection of master / slave statistics in a replication setup. In
+order to be able to get access to these statistics, the user needs special
+privileges. See the B<User> documentation above.
=item B<SlaveNotifications> I<true|false>