From 49ebc1acf0525d8e328b5e01622f34e65a2cf437 Mon Sep 17 00:00:00 2001
From: Florian Forster <octo@leeloo.lan.home.verplant.org>
Date: Sat, 20 Dec 2008 11:20:31 +0100
Subject: [PATCH] types.db(5): Explain in more detail how custom types should
 be added.

Apparently there was quite some confusion over this.
---
 src/types.db.pod | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

diff --git a/src/types.db.pod b/src/types.db.pod
index f0a49f6b..ef1550ca 100644
--- a/src/types.db.pod
+++ b/src/types.db.pod
@@ -29,9 +29,19 @@ happen. See L<rrdcreate(1)> for more details.
 =head1 FILES
 
 The location of the types.db file is defined by the B<TypesDB> configuration
-option (see L<collectd.conf(5)>). If you want to specify custom data-sets, you
-should do so by using a custom file specified as an additional argument to the
-B<TypesDB> option.
+option (see L<collectd.conf(5)>).
+
+=head1 CUSTOM TYPES
+
+If you want to specify custom types, you should do so by specifying a custom
+file in addition to the default one (see L<FILES>) above. You can do that by
+having multiple B<TypesDB> statements in your configuration file of by
+specifying more than one file in one line.
+
+For example:
+
+ TypesDB "/opt/collectd/share/collectd/types.db"
+ TypesDB "/opt/collectd/etc/types.db.custom"
 
 =head1 SEE ALSO
 
-- 
2.30.2