[collectd] Strange behavior of UnixSock plugin
jarle at bjorgeengen.net
Sat Dec 20 13:08:44 CET 2008
On Sat, 2008-12-20 at 11:23 +0100, Florian Forster wrote:
> Hi Jarle,
> On Sat, Dec 13, 2008 at 12:05:32PM +0100, Jarle Bjørgeengen wrote:
> > This was caused by the (custom) type missing from types.db. The reason
> > it was missing was of course because the yum/rpm upgrade process
> > overwrote types.db. Is there a types.db.local mechanism, to avoid this
> > in the future. I guess just changing the path to somewhere else in
> > collectd.conf also would do the trick, but then new upstream types
> > would have to be added manually ..
> yes, you can load multiple types.db files, precisely for this reason.
> I've updated the types.db(5) manual page to be more specific:
> -- 8< --
> diff --git a/src/types.db.pod b/src/types.db.pod
> index f0a49f6..ef1550c 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
> -- >8 --
> If you have further suggestions on how this could be explained better,
> please let me know :)
That seems very fine to me. Thanks.
More information about the collectd