[collectd] gmond plugin for collectd - part 2
Raymond Flanery
flaneryrejr at ornl.gov
Tue May 25 20:20:47 CEST 2010
Sometimes I just need to read my own posts! Sorry about that, forgot
that one had been the test
Sebastian Harl wrote:
> Hi Raymond,
>
> On Fri, May 21, 2010 at 02:55:29PM -0400, Raymond Flanery wrote:
>
>> If i try to exectute
>>
>> collectd -T
>>
>
> On Tue, May 25, 2010 at 01:56:40PM -0400, Raymond Flanery wrote:
>
>> Florian Forster wrote:
>>
>>> On Fri, May 21, 2010 at 02:55:29PM -0400, Raymond Flanery wrote:
>>>
>>>> May 21 14:52:54 node250 collectd[23920]: No read-functions are registered.
>>>> May 21 14:52:54 node250 collectd[23920]: Exiting normally.
>>>> May 21 14:52:54 node250 collectd[23920]: gmond plugin: Stopping receive thread.
>>>>
>>>> Am I wrong in thinking that the gmond plugin is a read-function?
>>>>
>>> Yes, the gmond plugin doesn't have a receive function, because it gets
>>> its data "asynchronously". It starts a new thread which waits for
>>> incoming network packages and dispatches them whenever it receives any.
>>> There is no "read function" which needs to be called periodically.
>>>
>
>
>> What you say makes sense about the plugin, however the other messages
>> that follow lead me to believe that the gmond plugin ceases to function
>> because of it. This of course would be something for me to worry about
>> since I need it to collect the mcast data.
>>
>
> That's caused by the '-T' command line option, which tells collectd to
> call all read callbacks once and then terminate. This is meant to be
> used, e.g., to test a configuration for errors. What did you expect that
> option to do?
>
> HTH,
> Sebastian
>
>
--
Raymond E. Flanery, Jr.
GIST Group, ORNL
865.574.0630
More information about the collectd
mailing list