Thanks for a good analysis. It matches my view of the issue.
I think the correct place to fix this is in munin-node-configure, or in
the surrounding code in the munin-node.postinst script.
It (and the plugins) has since been rewritten upstream in a more sane
manner to run the plugins with "autoconf" as argument, and use exit
codes from each plugin to figure out if the plugin should be installed
or not, and the output from stdout used for "--suggest --shell" symlink
hints.
In this case, one plugin that exits with a bad return code stops all
processing.
We should allow a plugin to return with a non-zero return code, and
ignore the plugin (but log the output) if so happens. It is possible
this may be backported from the upstream munin-node-configure, unless it
has been rewritten too much.
Attempting to autoconfigure the rest of the plugins may still produce
sensible result.
--
Stig Sandbeck Mathisen
ooo, shiny!
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
