Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

munin::node::configure::plugin(3pm) [debian man page]

Munin::Node::Configure::Plugin(3pm)			User Contributed Perl Documentation		       Munin::Node::Configure::Plugin(3pm)

NAME
Munin::Node::Configure::Plugin - Class representing a plugin, along with its installed and suggested services. SYNOPSIS
my $plugin = Munin::Node::Configure::Plugin->new(); METHODS
new(%args) Constructor. Required arguments are 'name' and 'path', which should be the basename and full path of the plugin, respectively. is_wildcard() Returns true if the plugin is a wildcard. In the case of SNMP plugins, only double-wild plugins will return true (ie. 'snmp__memory' would return false, but 'snmp__if_' would return true). is_snmp() Returns true if the plugin is an SNMP plugin. in_family(@families) Returns true if plugin's family is in @families, false otherwise. is_installed() Returns 'yes' if one or more links to this plugin exist in the service directory, 'no' otherwise. suggestion_string() Returns a string detailing whether or not autoconf considers that the plugin should be installed. The string may also report the reason why the plugin declined to be installed, or the list of suggestions it provided, if this information is available. installed_services_string() Returns a string detailing which wildcards are installed for this plugin. services_to_add() services_to_remove() Return a list of service names that should be added or removed for this plugin. add_instance($name) Associates a link from the service directory with this plugin. add_suggestions(@suggestions) Adds @suggestions to the list of suggested wildcards for this plugin. They are not validated. read_magic_markers() Sets the family and capabilities from the magic markers embedded in the plugin's executable, as specified by http://munin-monitoring.org/wiki/ConcisePlugins#Magicmarkers <http://munin-monitoring.org/wiki/ConcisePlugins#Magicmarkers> parse_autoconf_response(@response) Parses and validates the autoconf response from the plugin, in the format specified by http://munin-monitoring.org/wiki/ConcisePlugins#autoconf <http://munin-monitoring.org/wiki/ConcisePlugins#autoconf> Invalid input will cause an error to be logged against the plugin. parse_suggest_response(@response) Validates the suggestions from the plugin. Invalid suggestions will cause an error to be logged against the plugin. parse_snmpconf_response(@response) Parses and validates the snmpconf response from the plugin, in the format specified by http://munin-monitoring.org/wiki/ConcisePlugins#suggest <http://munin-monitoring.org/wiki/ConcisePlugins#suggest> Invalid or inconsistent input will cause an error to be logged against the plugin. log_error($message) Logs an error for later retrieval. The error will also be displayed if debugging output is enabled. perl v5.14.2 2013-11-12 Munin::Node::Configure::Plugin(3pm)

Check Out this Related Man Page

Dancer::Plugin(3pm)					User Contributed Perl Documentation				       Dancer::Plugin(3pm)

NAME
Dancer::Plugin - helper for writing Dancer plugins DESCRIPTION
Create plugins for Dancer SYNOPSIS
package Dancer::Plugin::LinkBlocker; use Dancer ':syntax'; use Dancer::Plugin; register block_links_from => sub { my $conf = plugin_setting(); my $re = join ('|', @{$conf->{hosts}}); before sub { if (request->referer && request->referer =~ /$re/) { status 403 || $conf->{http_code}; } }; }; register_plugin; 1; And in your application: package My::Webapp; use Dancer ':syntax'; use Dancer::Plugin::LinkBlocker; block_links_from; # this is exported by the plugin PLUGINS
You can extend Dancer by writing your own Plugin. A plugin is a module that exports a bunch of symbols to the current namespace (the caller will see all the symbols defined via "register"). Note that you have to "use" the plugin wherever you want to use its symbols. For instance, if you have Webapp::App1 and Webapp::App2, both loaded from your main application, they both need to "use FooPlugin" if they want to use the symbols exported by "FooPlugin". METHODS register Lets you define a keyword that will be exported by the plugin. register my_symbol_to_export => sub { # ... some code }; register_plugin A Dancer plugin must end with this statement. This lets the plugin register all the symbols define with "register" as exported symbols (via the Exporter module). A Dancer plugin inherits from Dancer::Plugin and Exporter transparently. plugin_setting Configuration for plugin should be structured like this in the config.yml of the application: plugins: plugin_name: key: value If "plugin_setting" is called inside a plugin, the appropriate configuration will be returned. The "plugin_name" should be the name of the package, or, if the plugin name is under the Dancer::Plugin:: namespace (which is recommended), the remaining part of the plugin name. Enclose the remaining part in quotes if it contains ::, e.g. for Dancer::Plugin::Foo::Bar, use: plugins: "Foo::Bar": key: value AUTHORS
This module has been written by Alexis Sukrieh and others. LICENSE
This module is free software and is published under the same terms as Perl itself. perl v5.14.2 2011-11-30 Dancer::Plugin(3pm)
Man Page