[collectd] Re-reading types.db and/or collectd.conf withouting restart collectd
kimor79 at yahoo.com
Thu Jan 10 18:20:00 CET 2013
Another good habit is to make use of the generic types (derive, gauge, percent, etc), so you don't have to edit types.db that often:
----- Original Message -----
> From: Yves Mettier <ymettier at free.fr>
> To: collectd at verplant.org
> Sent: Wednesday, January 9, 2013 11:58 PM
> Subject: Re: [collectd] Re-reading types.db and/or collectd.conf withouting restart collectd
> I agree...
> See the comments of https://github.com/collectd/collectd/pull/136 : this is not
> a new issue.
> About types.db, I suggest that you do not change it, but add your own file.
> In collectd.conf, you can specify more than one types.db file.
> When you upgrade collectd, you can replace the unmodified types.db with the new
> one and keep your addons in another file.
> Of course, this will not solve your problem about restarting collectd when you
> make a change.
> Le 2013-01-09 19:44, Daniel Hilst a écrit :
>> I have a problem. Every time I add a new type to types.db I have to
>> restart collectd. This lead to my nagios dashboard being fully red.
>> Any ideas of how re-read types.db without restarting?
>> I've this problem too while editing collectd.conf, but this is less
>> frequent.. I know that collectd keeps a AVL Tree cache, that
>> collectd-nagios reads from unix socket. Keeping cache entries between
>> restarts would solve that. What you people think?
>> When I say restart I mean receiving a SIGHUP.
> -- - Homepage - http://ymettier.free.fr -
> - GPG key - http://ymettier.free.fr/gpg.txt -
> - C en action - http://ymettier.free.fr/livres/C_en_action_ed2.html -
> - Guide Survie C - http://www.pearson.fr/livre/?GCOI=27440100673730 -
> collectd mailing list
> collectd at verplant.org
More information about the collectd