mirror of
https://github.com/munin-monitoring/contrib.git
synced 2025-07-25 02:18:08 +00:00
Whitespace cleanup
* remove trailing whitespace * remove empty lines at the end of files
This commit is contained in:
Lars Kruse
parent
ef851f0c34
commit
17f784270a
604 changed files with 2927 additions and 2945 deletions
|
|
@ -288,7 +288,7 @@ Linux machines running BOINC and munin-node
|
|||
|
||||
- or -
|
||||
|
||||
Linux servers (running munin-node) used to collect data from other systems
|
||||
Linux servers (running munin-node) used to collect data from other systems
|
||||
which are running BOINC, but not running munin-node (e.g. non-Linux systems)
|
||||
|
||||
=head1 CONFIGURATION
|
||||
|
|
@ -319,48 +319,48 @@ Warning level - minimum estimated work (default: 24.00 hours)
|
|||
|
||||
=item B<password>
|
||||
|
||||
Password for BOINC (default: none)
|
||||
Password for BOINC (default: none)
|
||||
|
||||
=back
|
||||
|
||||
=head2 B<Security Consideration:>
|
||||
|
||||
Using of variable B<password> poses a security risk. Even if the Munin
|
||||
configuration file for this plugin containing BOINC-password is properly
|
||||
protected, the password is exposed as environment variable and finally passed
|
||||
to boinccmd as a parameter. It is therefore possible for local users of the
|
||||
machine running this plugin to eavesdrop the BOINC password.
|
||||
Using of variable B<password> poses a security risk. Even if the Munin
|
||||
configuration file for this plugin containing BOINC-password is properly
|
||||
protected, the password is exposed as environment variable and finally passed
|
||||
to boinccmd as a parameter. It is therefore possible for local users of the
|
||||
machine running this plugin to eavesdrop the BOINC password.
|
||||
|
||||
Using of variable password is therefore strongly discouraged and is left here
|
||||
Using of variable password is therefore strongly discouraged and is left here
|
||||
as a legacy option and for testing purposes.
|
||||
|
||||
It should be always possible to use B<boincdir> variable instead - in such case
|
||||
the file gui_rpc_auth.cfg is read by boinccmd binary directly.
|
||||
If this plugin is used to fetch data from remote system, the gui_rpc_auth.cfg
|
||||
can be copied to special directory in a secure way (e.g. via scp) and properly
|
||||
It should be always possible to use B<boincdir> variable instead - in such case
|
||||
the file gui_rpc_auth.cfg is read by boinccmd binary directly.
|
||||
If this plugin is used to fetch data from remote system, the gui_rpc_auth.cfg
|
||||
can be copied to special directory in a secure way (e.g. via scp) and properly
|
||||
protected by file permissions.
|
||||
|
||||
=head1 INTERPRETATION
|
||||
|
||||
This plugin shows the estimated remaining computation time for all CPUs of
|
||||
This plugin shows the estimated remaining computation time for all CPUs of
|
||||
the machine and the estimated remaining computation time of longest workunit.
|
||||
The estimation is based on assumption that the workunits of different lengths
|
||||
The estimation is based on assumption that the workunits of different lengths
|
||||
will be distributed to the CPUs evenly (which is not always the case).
|
||||
|
||||
The warning level can be used to warn in forward about the risk of workunits
|
||||
The warning level can be used to warn in forward about the risk of workunits
|
||||
local cache depletion and BOINC client running out of the work.
|
||||
Although such warning can be achieved by configuring Munin master, there is
|
||||
Although such warning can be achieved by configuring Munin master, there is
|
||||
also this option to configure it on munin-node side.
|
||||
|
||||
=head1 EXAMPLES
|
||||
|
||||
=head2 Local BOINC Example
|
||||
|
||||
BOINC is running on local machine. The BOINC binaries are installed in
|
||||
BOINC is running on local machine. The BOINC binaries are installed in
|
||||
F</opt/boinc/custom-6.10.1/>, the BOINC is running in directory
|
||||
F</usr/local/boinc/> under username boinc, group boinc and the password is used
|
||||
F</usr/local/boinc/> under username boinc, group boinc and the password is used
|
||||
to protect access to BOINC.
|
||||
Warning will be set when estimated work for any of CPUs will decrease under
|
||||
Warning will be set when estimated work for any of CPUs will decrease under
|
||||
48 hours:
|
||||
|
||||
[boinc_*]
|
||||
|
|
@ -371,17 +371,17 @@ Warning will be set when estimated work for any of CPUs will decrease under
|
|||
|
||||
=head2 Remote BOINC Example
|
||||
|
||||
BOINC is running on 2 remote machines C<foo> and C<bar>.
|
||||
On the local machine the binary of command-line interface is installed in
|
||||
BOINC is running on 2 remote machines C<foo> and C<bar>.
|
||||
On the local machine the binary of command-line interface is installed in
|
||||
directory F</usr/local/bin/>.
|
||||
The BOINC password used on the remote machine C<foo> is stored in file
|
||||
The BOINC password used on the remote machine C<foo> is stored in file
|
||||
F</etc/munin/boinc/foo/gui_rpc_auth.cfg>.
|
||||
The BOINC password used on the remote machine C<bar> is stored in file
|
||||
The BOINC password used on the remote machine C<bar> is stored in file
|
||||
F</etc/munin/boinc/bar/gui_rpc_auth.cfg>.
|
||||
These files are owned and readable by root, readable by group munin and not
|
||||
readable by others.
|
||||
There are 2 symbolic links to this plugin created in the munin plugins
|
||||
directory (usually F</etc/munin/plugins/>): F<snmp_foo_boincestwk> and
|
||||
These files are owned and readable by root, readable by group munin and not
|
||||
readable by others.
|
||||
There are 2 symbolic links to this plugin created in the munin plugins
|
||||
directory (usually F</etc/munin/plugins/>): F<snmp_foo_boincestwk> and
|
||||
F<snmp_bar_boincestwk>
|
||||
|
||||
[snmp_foo_boinc*]
|
||||
|
|
@ -396,33 +396,33 @@ F<snmp_bar_boincestwk>
|
|||
env.host bar
|
||||
env.boincdir /etc/munin/boinc/bar
|
||||
|
||||
This way the plugin can be used by Munin the same way as the Munin plugins
|
||||
This way the plugin can be used by Munin the same way as the Munin plugins
|
||||
utilizng SNMP (although this plugin itself does not use SNMP).
|
||||
|
||||
=head1 BUGS
|
||||
|
||||
The estimation is based on simple assumption, that longest workunits will be
|
||||
processed first. This is the case when work is distributed evenly among CPUs.
|
||||
But this is not always the case, because various deadlines for various
|
||||
workunits may fire the "panic mode" of BOINC and scheduling could be much
|
||||
different.
|
||||
For example, there can be 4 CPUs, and BOINC having downloaded 4 workunits
|
||||
with estimated run-time 1 hour each and 3 workunits with estimated run-time
|
||||
4 hours each.
|
||||
The estimation is based on simple assumption, that longest workunits will be
|
||||
processed first. This is the case when work is distributed evenly among CPUs.
|
||||
But this is not always the case, because various deadlines for various
|
||||
workunits may fire the "panic mode" of BOINC and scheduling could be much
|
||||
different.
|
||||
For example, there can be 4 CPUs, and BOINC having downloaded 4 workunits
|
||||
with estimated run-time 1 hour each and 3 workunits with estimated run-time
|
||||
4 hours each.
|
||||
This Munin plugin will report estimated work 4 hours for each CPU.
|
||||
But if deadline of those 1-hour workunits will be much shorter than deadline
|
||||
of those 4-hours workunits, BOINC will schedule short workunits first (for all
|
||||
But if deadline of those 1-hour workunits will be much shorter than deadline
|
||||
of those 4-hours workunits, BOINC will schedule short workunits first (for all
|
||||
4 CPUs) and after finishing them it will schedule those long workunits.
|
||||
This will result in real computation for 5 hours on 3 CPUs but only 1 hour on
|
||||
remaining 4th CPU. So after 1 hour of computation 1 of CPUs will run out of
|
||||
remaining 4th CPU. So after 1 hour of computation 1 of CPUs will run out of
|
||||
work.
|
||||
|
||||
There is no C<autoconf> capability at the moment. This is due to the fact, that
|
||||
BOINC installations may vary over different systems, sometimes using default
|
||||
directory from distribution (e.g. F</var/lib/boinc/> in Debian or Ubuntu), but
|
||||
There is no C<autoconf> capability at the moment. This is due to the fact, that
|
||||
BOINC installations may vary over different systems, sometimes using default
|
||||
directory from distribution (e.g. F</var/lib/boinc/> in Debian or Ubuntu), but
|
||||
often running in user directories or in other separate directories.
|
||||
Also the user-ID under which BOINC runs often differs.
|
||||
Under these circumstances the C<autoconf> would be either lame or too
|
||||
Also the user-ID under which BOINC runs often differs.
|
||||
Under these circumstances the C<autoconf> would be either lame or too
|
||||
complicated.
|
||||
|
||||
=head1 AUTHOR
|
||||
|
|
|
|||
|
|
@ -5,12 +5,12 @@
|
|||
# Parameters:
|
||||
#
|
||||
# password -- The password for RPC authentication
|
||||
# (default: boinc_cmd will look for a file
|
||||
# (default: boinc_cmd will look for a file
|
||||
# 'gui_rpc_auth.cfg' and use the password in it)
|
||||
# host -- the host to connect to (default: localhost)
|
||||
# port -- optional (default: 31416)
|
||||
#
|
||||
# This plugin can monitor boinc processes running on local/remote machines.
|
||||
# This plugin can monitor boinc processes running on local/remote machines.
|
||||
# You can see the progress on various projects.
|
||||
#
|
||||
# Author: Petr Ruzicka <petr.ruzicka@gmail.com>
|
||||
|
|
@ -49,14 +49,14 @@ sub autoconf {
|
|||
|
||||
$reply =~ /<nonce>(.*)<\/nonce>/;
|
||||
$hash = md5_hex($1, $password);
|
||||
|
||||
|
||||
print $client "<boinc_gui_rpc_request><auth2><nonce_hash>$hash</nonce_hash></auth2></boinc_gui_rpc_request>\003";
|
||||
|
||||
|
||||
{
|
||||
local $/ = "\003";
|
||||
$reply = <$client>;
|
||||
}
|
||||
|
||||
|
||||
if ($reply =~ /<authorized\/>/) {
|
||||
print "yes\n";
|
||||
exit 0;
|
||||
|
|
@ -70,29 +70,29 @@ sub config {
|
|||
my $client = IO::Socket::INET->new ( PeerAddr => $host,
|
||||
PeerPort => $port,
|
||||
Proto => 'tcp' )
|
||||
or die "Can't bind : $@\n";
|
||||
or die "Can't bind : $@\n";
|
||||
|
||||
print $client "<boinc_gui_rpc_request><auth1/></boinc_gui_rpc_request>\003";
|
||||
|
||||
{
|
||||
{
|
||||
local $/ = "\003";
|
||||
$reply = <$client>;
|
||||
}
|
||||
|
||||
$reply =~ /<nonce>(.*)<\/nonce>/;
|
||||
my $hash = md5_hex($1, $password);
|
||||
|
||||
|
||||
print $client "<boinc_gui_rpc_request><auth2><nonce_hash>$hash</nonce_hash></auth2></boinc_gui_rpc_request>\003";
|
||||
|
||||
|
||||
{
|
||||
local $/ = "\003";
|
||||
$reply = <$client>;
|
||||
}
|
||||
|
||||
|
||||
if ($reply !~ /<authorized\/>/) {
|
||||
die "Wrong password: $_";
|
||||
}
|
||||
|
||||
|
||||
print $client "<boinc_gui_rpc_request><get_state></boinc_gui_rpc_request>";
|
||||
|
||||
while (chomp($reply = <$client>) && ($reply ne "</boinc_gui_rpc_reply>")) {
|
||||
|
|
@ -101,7 +101,7 @@ sub config {
|
|||
print "graph_category htc\n";
|
||||
print "graph_args -l 0\n";
|
||||
print "graph_vlabel %\n";
|
||||
}
|
||||
}
|
||||
if ($reply =~ /<project_name>(.*)<\/project_name>/) {
|
||||
my $boinc_munin_name=$1;
|
||||
$boinc_munin_name =~ /(\w+).*/;
|
||||
|
|
@ -115,31 +115,31 @@ sub report {
|
|||
my $client = IO::Socket::INET->new ( PeerAddr => $host,
|
||||
PeerPort => $port,
|
||||
Proto => 'tcp' )
|
||||
or die "Can't bind : $@\n";
|
||||
or die "Can't bind : $@\n";
|
||||
|
||||
print $client "<boinc_gui_rpc_request><auth1/></boinc_gui_rpc_request>\003";
|
||||
|
||||
{
|
||||
{
|
||||
local $/ = "\003";
|
||||
$reply = <$client>;
|
||||
}
|
||||
|
||||
$reply =~ /<nonce>(.*)<\/nonce>/;
|
||||
my $hash = md5_hex($1, $password);
|
||||
|
||||
|
||||
print $client "<boinc_gui_rpc_request><auth2><nonce_hash>$hash</nonce_hash></auth2></boinc_gui_rpc_request>\003";
|
||||
|
||||
|
||||
{
|
||||
local $/ = "\003";
|
||||
$reply = <$client>;
|
||||
}
|
||||
|
||||
|
||||
if ($reply !~ /<authorized\/>/) {
|
||||
die "Wrong password: $_";
|
||||
}
|
||||
|
||||
|
||||
print $client "<boinc_gui_rpc_request><get_state></boinc_gui_rpc_request>";
|
||||
|
||||
|
||||
while (chomp($reply = <$client>) && ($reply ne "</boinc_gui_rpc_reply>")) {
|
||||
if ($reply =~ /<project_name>(\w+).*<\/project_name>/) {
|
||||
$project = $1;
|
||||
|
|
|
|||
|
|
@ -279,7 +279,7 @@ Linux machines running BOINC and munin-node
|
|||
|
||||
- or -
|
||||
|
||||
Linux servers (running munin-node) used to collect data from other systems
|
||||
Linux servers (running munin-node) used to collect data from other systems
|
||||
which are running BOINC, but not running munin-node (e.g. non-Linux systems)
|
||||
|
||||
=head1 CONFIGURATION
|
||||
|
|
@ -306,40 +306,40 @@ Directory containing appropriate file gui_rpc_auth.cfg (default: none)
|
|||
|
||||
=item B<password>
|
||||
|
||||
Password for BOINC (default: none)
|
||||
Password for BOINC (default: none)
|
||||
|
||||
=back
|
||||
|
||||
=head2 B<Security Consideration:>
|
||||
|
||||
Using of variable B<password> poses a security risk. Even if the Munin
|
||||
configuration file for this plugin containing BOINC-password is properly
|
||||
protected, the password is exposed as environment variable and finally passed
|
||||
to boinccmd as a parameter. It is therefore possible for local users of the
|
||||
machine running this plugin to eavesdrop the BOINC password.
|
||||
Using of variable B<password> poses a security risk. Even if the Munin
|
||||
configuration file for this plugin containing BOINC-password is properly
|
||||
protected, the password is exposed as environment variable and finally passed
|
||||
to boinccmd as a parameter. It is therefore possible for local users of the
|
||||
machine running this plugin to eavesdrop the BOINC password.
|
||||
|
||||
Using of variable password is therefore strongly discouraged and is left here
|
||||
Using of variable password is therefore strongly discouraged and is left here
|
||||
as a legacy option and for testing purposes.
|
||||
|
||||
It should be always possible to use B<boincdir> variable instead - in such case
|
||||
the file gui_rpc_auth.cfg is read by boinccmd binary directly.
|
||||
If this plugin is used to fetch data from remote system, the gui_rpc_auth.cfg
|
||||
can be copied to special directory in a secure way (e.g. via scp) and properly
|
||||
It should be always possible to use B<boincdir> variable instead - in such case
|
||||
the file gui_rpc_auth.cfg is read by boinccmd binary directly.
|
||||
If this plugin is used to fetch data from remote system, the gui_rpc_auth.cfg
|
||||
can be copied to special directory in a secure way (e.g. via scp) and properly
|
||||
protected by file permissions.
|
||||
|
||||
=head1 INTERPRETATION
|
||||
|
||||
This plugin shows the number of currently running BOINC tasks on the machine.
|
||||
If machine is attached to several BOINC projects, data for all these projects
|
||||
This plugin shows the number of currently running BOINC tasks on the machine.
|
||||
If machine is attached to several BOINC projects, data for all these projects
|
||||
are displayed.
|
||||
|
||||
=head1 EXAMPLES
|
||||
|
||||
=head2 Local BOINC Example
|
||||
|
||||
BOINC is running on local machine. The BOINC binaries are installed in
|
||||
BOINC is running on local machine. The BOINC binaries are installed in
|
||||
F</opt/boinc/custom-6.10.1/>, the BOINC is running in directory
|
||||
F</usr/local/boinc/> under username boinc, group boinc and the password is used
|
||||
F</usr/local/boinc/> under username boinc, group boinc and the password is used
|
||||
to protect access to BOINC:
|
||||
|
||||
[boinc_*]
|
||||
|
|
@ -349,17 +349,17 @@ to protect access to BOINC:
|
|||
|
||||
=head2 Remote BOINC Example
|
||||
|
||||
BOINC is running on 2 remote machines C<foo> and C<bar>.
|
||||
On the local machine the binary of command-line interface is installed in
|
||||
BOINC is running on 2 remote machines C<foo> and C<bar>.
|
||||
On the local machine the binary of command-line interface is installed in
|
||||
directory F</usr/local/bin/>.
|
||||
The BOINC password used on the remote machine C<foo> is stored in file
|
||||
The BOINC password used on the remote machine C<foo> is stored in file
|
||||
F</etc/munin/boinc/foo/gui_rpc_auth.cfg>.
|
||||
The BOINC password used on the remote machine C<bar> is stored in file
|
||||
The BOINC password used on the remote machine C<bar> is stored in file
|
||||
F</etc/munin/boinc/bar/gui_rpc_auth.cfg>.
|
||||
These files are owned and readable by root, readable by group munin and not
|
||||
readable by others.
|
||||
There are 2 symbolic links to this plugin created in the munin plugins
|
||||
directory (usually F</etc/munin/plugins/>): F<boincprojs_foo> and
|
||||
These files are owned and readable by root, readable by group munin and not
|
||||
readable by others.
|
||||
There are 2 symbolic links to this plugin created in the munin plugins
|
||||
directory (usually F</etc/munin/plugins/>): F<boincprojs_foo> and
|
||||
F<boincprojs_bar>
|
||||
|
||||
[boincprojs_foo]
|
||||
|
|
@ -379,12 +379,12 @@ SNMP and IPMI plugins.
|
|||
|
||||
=head1 BUGS
|
||||
|
||||
There is no C<autoconf> capability at the moment. This is due to the fact, that
|
||||
BOINC installations may vary over different systems, sometimes using default
|
||||
directory from distribution (e.g. F</var/lib/boinc/> in Debian or Ubuntu), but
|
||||
There is no C<autoconf> capability at the moment. This is due to the fact, that
|
||||
BOINC installations may vary over different systems, sometimes using default
|
||||
directory from distribution (e.g. F</var/lib/boinc/> in Debian or Ubuntu), but
|
||||
often running in user directories or in other separate directories.
|
||||
Also the user-ID under which BOINC runs often differs.
|
||||
Under these circumstances the C<autoconf> would be either lame or too
|
||||
Also the user-ID under which BOINC runs often differs.
|
||||
Under these circumstances the C<autoconf> would be either lame or too
|
||||
complicated.
|
||||
|
||||
=head1 AUTHOR
|
||||
|
|
|
|||
|
|
@ -317,7 +317,7 @@ Linux machines running BOINC and munin-node
|
|||
|
||||
- or -
|
||||
|
||||
Linux servers (running munin-node) used to collect data from other systems
|
||||
Linux servers (running munin-node) used to collect data from other systems
|
||||
which are running BOINC, but not running munin-node (e.g. non-Linux systems)
|
||||
|
||||
=head1 CONFIGURATION
|
||||
|
|
@ -348,45 +348,45 @@ Display unusual states details (default: 0 = Summarize unusual states as C<other
|
|||
|
||||
=item B<password>
|
||||
|
||||
Password for BOINC (default: none)
|
||||
Password for BOINC (default: none)
|
||||
|
||||
=back
|
||||
|
||||
=head2 B<Security Consideration:>
|
||||
|
||||
Using of variable B<password> poses a security risk. Even if the Munin
|
||||
configuration file for this plugin containing BOINC-password is properly
|
||||
protected, the password is exposed as environment variable and finally passed
|
||||
to boinccmd as a parameter. It is therefore possible for local users of the
|
||||
machine running this plugin to eavesdrop the BOINC password.
|
||||
Using of variable B<password> poses a security risk. Even if the Munin
|
||||
configuration file for this plugin containing BOINC-password is properly
|
||||
protected, the password is exposed as environment variable and finally passed
|
||||
to boinccmd as a parameter. It is therefore possible for local users of the
|
||||
machine running this plugin to eavesdrop the BOINC password.
|
||||
|
||||
Using of variable password is therefore strongly discouraged and is left here
|
||||
Using of variable password is therefore strongly discouraged and is left here
|
||||
as a legacy option and for testing purposes.
|
||||
|
||||
It should be always possible to use B<boincdir> variable instead - in such case
|
||||
the file gui_rpc_auth.cfg is read by boinccmd binary directly.
|
||||
If this plugin is used to fetch data from remote system, the gui_rpc_auth.cfg
|
||||
can be copied to special directory in a secure way (e.g. via scp) and properly
|
||||
It should be always possible to use B<boincdir> variable instead - in such case
|
||||
the file gui_rpc_auth.cfg is read by boinccmd binary directly.
|
||||
If this plugin is used to fetch data from remote system, the gui_rpc_auth.cfg
|
||||
can be copied to special directory in a secure way (e.g. via scp) and properly
|
||||
protected by file permissions.
|
||||
|
||||
=head1 INTERPRETATION
|
||||
|
||||
This plugin shows how many BOINC workunits are in all the various states.
|
||||
The most important states C<Running>, C<Preempted>, C<Suspended>,
|
||||
C<Ready to run>, C<Ready to report>, C<Downloading> and C<Uploading> are always
|
||||
This plugin shows how many BOINC workunits are in all the various states.
|
||||
The most important states C<Running>, C<Preempted>, C<Suspended>,
|
||||
C<Ready to run>, C<Ready to report>, C<Downloading> and C<Uploading> are always
|
||||
displayed. All other states are shown as C<other>.
|
||||
|
||||
If the variable B<verbose> is used, additionally also states
|
||||
C<Computation Error> and C<Aborted> are shown separately (they are included in
|
||||
C<other> otherwise).
|
||||
If the variable B<verbose> is used, additionally also states
|
||||
C<Computation Error> and C<Aborted> are shown separately (they are included in
|
||||
C<other> otherwise).
|
||||
|
||||
=head1 EXAMPLES
|
||||
|
||||
=head2 Local BOINC Example
|
||||
|
||||
BOINC is running on local machine. The BOINC binaries are installed in
|
||||
BOINC is running on local machine. The BOINC binaries are installed in
|
||||
F</opt/boinc/custom-6.10.1/>, the BOINC is running in directory
|
||||
F</usr/local/boinc/> under username boinc, group boinc and the password is used
|
||||
F</usr/local/boinc/> under username boinc, group boinc and the password is used
|
||||
to protect access to BOINC:
|
||||
|
||||
[boinc_*]
|
||||
|
|
@ -397,17 +397,17 @@ to protect access to BOINC:
|
|||
|
||||
=head2 Remote BOINC Example
|
||||
|
||||
BOINC is running on 2 remote machines C<foo> and C<bar>.
|
||||
On the local machine the binary of command-line interface is installed in
|
||||
BOINC is running on 2 remote machines C<foo> and C<bar>.
|
||||
On the local machine the binary of command-line interface is installed in
|
||||
directory F</usr/local/bin/>.
|
||||
The BOINC password used on the remote machine C<foo> is stored in file
|
||||
The BOINC password used on the remote machine C<foo> is stored in file
|
||||
F</etc/munin/boinc/foo/gui_rpc_auth.cfg>.
|
||||
The BOINC password used on the remote machine C<bar> is stored in file
|
||||
The BOINC password used on the remote machine C<bar> is stored in file
|
||||
F</etc/munin/boinc/bar/gui_rpc_auth.cfg>.
|
||||
These files are owned and readable by root, readable by group munin and not
|
||||
readable by others.
|
||||
There are 2 symbolic links to this plugin created in the munin plugins
|
||||
directory (usually F</etc/munin/plugins/>): F<snmp_foo_boincwus> and
|
||||
These files are owned and readable by root, readable by group munin and not
|
||||
readable by others.
|
||||
There are 2 symbolic links to this plugin created in the munin plugins
|
||||
directory (usually F</etc/munin/plugins/>): F<snmp_foo_boincwus> and
|
||||
F<snmp_bar_boincwus>
|
||||
|
||||
[snmp_foo_boinc*]
|
||||
|
|
@ -422,17 +422,17 @@ F<snmp_bar_boincwus>
|
|||
env.host bar
|
||||
env.boincdir /etc/munin/boinc/bar
|
||||
|
||||
This way the plugin can be used by Munin the same way as the Munin plugins
|
||||
This way the plugin can be used by Munin the same way as the Munin plugins
|
||||
utilizng SNMP (although this plugin itself does not use SNMP).
|
||||
|
||||
=head1 BUGS
|
||||
|
||||
There is no C<autoconf> capability at the moment. This is due to the fact, that
|
||||
BOINC installations may vary over different systems, sometimes using default
|
||||
directory from distribution (e.g. F</var/lib/boinc/> in Debian or Ubuntu), but
|
||||
There is no C<autoconf> capability at the moment. This is due to the fact, that
|
||||
BOINC installations may vary over different systems, sometimes using default
|
||||
directory from distribution (e.g. F</var/lib/boinc/> in Debian or Ubuntu), but
|
||||
often running in user directories or in other separate directories.
|
||||
Also the user-ID under which BOINC runs often differs.
|
||||
Under these circumstances the C<autoconf> would be either lame or too
|
||||
Also the user-ID under which BOINC runs often differs.
|
||||
Under these circumstances the C<autoconf> would be either lame or too
|
||||
complicated.
|
||||
|
||||
=head1 AUTHOR
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue