Révision 17f78427
Whitespace cleanup
- remove trailing whitespace
- remove empty lines at the end of files
| plugins/boinc/boinc_wus | ||
|---|---|---|
| 317 | 317 |
|
| 318 | 318 |
- or - |
| 319 | 319 |
|
| 320 |
Linux servers (running munin-node) used to collect data from other systems
|
|
| 320 |
Linux servers (running munin-node) used to collect data from other systems |
|
| 321 | 321 |
which are running BOINC, but not running munin-node (e.g. non-Linux systems) |
| 322 | 322 |
|
| 323 | 323 |
=head1 CONFIGURATION |
| ... | ... | |
| 348 | 348 |
|
| 349 | 349 |
=item B<password> |
| 350 | 350 |
|
| 351 |
Password for BOINC (default: none)
|
|
| 351 |
Password for BOINC (default: none) |
|
| 352 | 352 |
|
| 353 | 353 |
=back |
| 354 | 354 |
|
| 355 | 355 |
=head2 B<Security Consideration:> |
| 356 | 356 |
|
| 357 |
Using of variable B<password> poses a security risk. Even if the Munin
|
|
| 358 |
configuration file for this plugin containing BOINC-password is properly
|
|
| 359 |
protected, the password is exposed as environment variable and finally passed
|
|
| 360 |
to boinccmd as a parameter. It is therefore possible for local users of the
|
|
| 361 |
machine running this plugin to eavesdrop the BOINC password.
|
|
| 357 |
Using of variable B<password> poses a security risk. Even if the Munin |
|
| 358 |
configuration file for this plugin containing BOINC-password is properly |
|
| 359 |
protected, the password is exposed as environment variable and finally passed |
|
| 360 |
to boinccmd as a parameter. It is therefore possible for local users of the |
|
| 361 |
machine running this plugin to eavesdrop the BOINC password. |
|
| 362 | 362 |
|
| 363 |
Using of variable password is therefore strongly discouraged and is left here
|
|
| 363 |
Using of variable password is therefore strongly discouraged and is left here |
|
| 364 | 364 |
as a legacy option and for testing purposes. |
| 365 | 365 |
|
| 366 |
It should be always possible to use B<boincdir> variable instead - in such case
|
|
| 367 |
the file gui_rpc_auth.cfg is read by boinccmd binary directly.
|
|
| 368 |
If this plugin is used to fetch data from remote system, the gui_rpc_auth.cfg
|
|
| 369 |
can be copied to special directory in a secure way (e.g. via scp) and properly
|
|
| 366 |
It should be always possible to use B<boincdir> variable instead - in such case |
|
| 367 |
the file gui_rpc_auth.cfg is read by boinccmd binary directly. |
|
| 368 |
If this plugin is used to fetch data from remote system, the gui_rpc_auth.cfg |
|
| 369 |
can be copied to special directory in a secure way (e.g. via scp) and properly |
|
| 370 | 370 |
protected by file permissions. |
| 371 | 371 |
|
| 372 | 372 |
=head1 INTERPRETATION |
| 373 | 373 |
|
| 374 |
This plugin shows how many BOINC workunits are in all the various states.
|
|
| 375 |
The most important states C<Running>, C<Preempted>, C<Suspended>,
|
|
| 376 |
C<Ready to run>, C<Ready to report>, C<Downloading> and C<Uploading> are always
|
|
| 374 |
This plugin shows how many BOINC workunits are in all the various states. |
|
| 375 |
The most important states C<Running>, C<Preempted>, C<Suspended>, |
|
| 376 |
C<Ready to run>, C<Ready to report>, C<Downloading> and C<Uploading> are always |
|
| 377 | 377 |
displayed. All other states are shown as C<other>. |
| 378 | 378 |
|
| 379 |
If the variable B<verbose> is used, additionally also states
|
|
| 380 |
C<Computation Error> and C<Aborted> are shown separately (they are included in
|
|
| 381 |
C<other> otherwise).
|
|
| 379 |
If the variable B<verbose> is used, additionally also states |
|
| 380 |
C<Computation Error> and C<Aborted> are shown separately (they are included in |
|
| 381 |
C<other> otherwise). |
|
| 382 | 382 |
|
| 383 | 383 |
=head1 EXAMPLES |
| 384 | 384 |
|
| 385 | 385 |
=head2 Local BOINC Example |
| 386 | 386 |
|
| 387 |
BOINC is running on local machine. The BOINC binaries are installed in
|
|
| 387 |
BOINC is running on local machine. The BOINC binaries are installed in |
|
| 388 | 388 |
F</opt/boinc/custom-6.10.1/>, the BOINC is running in directory |
| 389 |
F</usr/local/boinc/> under username boinc, group boinc and the password is used
|
|
| 389 |
F</usr/local/boinc/> under username boinc, group boinc and the password is used |
|
| 390 | 390 |
to protect access to BOINC: |
| 391 | 391 |
|
| 392 | 392 |
[boinc_*] |
| ... | ... | |
| 397 | 397 |
|
| 398 | 398 |
=head2 Remote BOINC Example |
| 399 | 399 |
|
| 400 |
BOINC is running on 2 remote machines C<foo> and C<bar>.
|
|
| 401 |
On the local machine the binary of command-line interface is installed in
|
|
| 400 |
BOINC is running on 2 remote machines C<foo> and C<bar>. |
|
| 401 |
On the local machine the binary of command-line interface is installed in |
|
| 402 | 402 |
directory F</usr/local/bin/>. |
| 403 |
The BOINC password used on the remote machine C<foo> is stored in file
|
|
| 403 |
The BOINC password used on the remote machine C<foo> is stored in file |
|
| 404 | 404 |
F</etc/munin/boinc/foo/gui_rpc_auth.cfg>. |
| 405 |
The BOINC password used on the remote machine C<bar> is stored in file
|
|
| 405 |
The BOINC password used on the remote machine C<bar> is stored in file |
|
| 406 | 406 |
F</etc/munin/boinc/bar/gui_rpc_auth.cfg>. |
| 407 |
These files are owned and readable by root, readable by group munin and not
|
|
| 408 |
readable by others.
|
|
| 409 |
There are 2 symbolic links to this plugin created in the munin plugins
|
|
| 410 |
directory (usually F</etc/munin/plugins/>): F<snmp_foo_boincwus> and
|
|
| 407 |
These files are owned and readable by root, readable by group munin and not |
|
| 408 |
readable by others. |
|
| 409 |
There are 2 symbolic links to this plugin created in the munin plugins |
|
| 410 |
directory (usually F</etc/munin/plugins/>): F<snmp_foo_boincwus> and |
|
| 411 | 411 |
F<snmp_bar_boincwus> |
| 412 | 412 |
|
| 413 | 413 |
[snmp_foo_boinc*] |
| ... | ... | |
| 422 | 422 |
env.host bar |
| 423 | 423 |
env.boincdir /etc/munin/boinc/bar |
| 424 | 424 |
|
| 425 |
This way the plugin can be used by Munin the same way as the Munin plugins
|
|
| 425 |
This way the plugin can be used by Munin the same way as the Munin plugins |
|
| 426 | 426 |
utilizng SNMP (although this plugin itself does not use SNMP). |
| 427 | 427 |
|
| 428 | 428 |
=head1 BUGS |
| 429 | 429 |
|
| 430 |
There is no C<autoconf> capability at the moment. This is due to the fact, that
|
|
| 431 |
BOINC installations may vary over different systems, sometimes using default
|
|
| 432 |
directory from distribution (e.g. F</var/lib/boinc/> in Debian or Ubuntu), but
|
|
| 430 |
There is no C<autoconf> capability at the moment. This is due to the fact, that |
|
| 431 |
BOINC installations may vary over different systems, sometimes using default |
|
| 432 |
directory from distribution (e.g. F</var/lib/boinc/> in Debian or Ubuntu), but |
|
| 433 | 433 |
often running in user directories or in other separate directories. |
| 434 |
Also the user-ID under which BOINC runs often differs.
|
|
| 435 |
Under these circumstances the C<autoconf> would be either lame or too
|
|
| 434 |
Also the user-ID under which BOINC runs often differs. |
|
| 435 |
Under these circumstances the C<autoconf> would be either lame or too |
|
| 436 | 436 |
complicated. |
| 437 | 437 |
|
| 438 | 438 |
=head1 AUTHOR |
Formats disponibles : Unified diff