author | Sebastian Harl <sh@tokkee.org> | |
Wed, 26 Mar 2008 08:28:40 +0000 (09:28 +0100) | ||
committer | Florian Forster <octo@huhu.verplant.org> | |
Wed, 26 Mar 2008 08:28:40 +0000 (09:28 +0100) | ||
commit | 90287c6d240a168fca8d01f8330e2e2263e1f0a4 | |
tree | 5fa16a48f2a02ed6f1c14f513b67e7ac7d053a72 | tree | snapshot |
parent | 056474c91e21ff051d2851f7a07e4f83b7e6d74f | commit | diff |
Disambiguated the protocol used by the unixsock (and other) plugins.
As discussed with Florian on IRC, the interpretation of the status line
returned by the unixsock plugin (et.al.) is now strictly specified. A status
greater than or equal to zero indicates success and the number of subsequent
lines of output. A negative status still indicates failure.
This way, frontends can manage the output without having to know any
command-specific interpretation rules.
The GETVAL command has been updated to implement this specification. It now
returns each value on a separate line. collectd-unixsock(5) has been updated
to reflect the changes.
Signed-off-by: Sebastian Harl <sh@tokkee.org>
Signed-off-by: Florian Forster <octo@huhu.verplant.org>
As discussed with Florian on IRC, the interpretation of the status line
returned by the unixsock plugin (et.al.) is now strictly specified. A status
greater than or equal to zero indicates success and the number of subsequent
lines of output. A negative status still indicates failure.
This way, frontends can manage the output without having to know any
command-specific interpretation rules.
The GETVAL command has been updated to implement this specification. It now
returns each value on a separate line. collectd-unixsock(5) has been updated
to reflect the changes.
Signed-off-by: Sebastian Harl <sh@tokkee.org>
Signed-off-by: Florian Forster <octo@huhu.verplant.org>
src/collectd-unixsock.pod | diff | blob | history | |
src/utils_cmd_getval.c | diff | blob | history | |
src/utils_cmd_listval.c | diff | blob | history |