Révision 17f78427
Whitespace cleanup
- remove trailing whitespace
- remove empty lines at the end of files
| plugins/boinc/boinc_projs | ||
|---|---|---|
| 279 | 279 |
|
| 280 | 280 |
- or - |
| 281 | 281 |
|
| 282 |
Linux servers (running munin-node) used to collect data from other systems
|
|
| 282 |
Linux servers (running munin-node) used to collect data from other systems |
|
| 283 | 283 |
which are running BOINC, but not running munin-node (e.g. non-Linux systems) |
| 284 | 284 |
|
| 285 | 285 |
=head1 CONFIGURATION |
| ... | ... | |
| 306 | 306 |
|
| 307 | 307 |
=item B<password> |
| 308 | 308 |
|
| 309 |
Password for BOINC (default: none)
|
|
| 309 |
Password for BOINC (default: none) |
|
| 310 | 310 |
|
| 311 | 311 |
=back |
| 312 | 312 |
|
| 313 | 313 |
=head2 B<Security Consideration:> |
| 314 | 314 |
|
| 315 |
Using of variable B<password> poses a security risk. Even if the Munin
|
|
| 316 |
configuration file for this plugin containing BOINC-password is properly
|
|
| 317 |
protected, the password is exposed as environment variable and finally passed
|
|
| 318 |
to boinccmd as a parameter. It is therefore possible for local users of the
|
|
| 319 |
machine running this plugin to eavesdrop the BOINC password.
|
|
| 315 |
Using of variable B<password> poses a security risk. Even if the Munin |
|
| 316 |
configuration file for this plugin containing BOINC-password is properly |
|
| 317 |
protected, the password is exposed as environment variable and finally passed |
|
| 318 |
to boinccmd as a parameter. It is therefore possible for local users of the |
|
| 319 |
machine running this plugin to eavesdrop the BOINC password. |
|
| 320 | 320 |
|
| 321 |
Using of variable password is therefore strongly discouraged and is left here
|
|
| 321 |
Using of variable password is therefore strongly discouraged and is left here |
|
| 322 | 322 |
as a legacy option and for testing purposes. |
| 323 | 323 |
|
| 324 |
It should be always possible to use B<boincdir> variable instead - in such case
|
|
| 325 |
the file gui_rpc_auth.cfg is read by boinccmd binary directly.
|
|
| 326 |
If this plugin is used to fetch data from remote system, the gui_rpc_auth.cfg
|
|
| 327 |
can be copied to special directory in a secure way (e.g. via scp) and properly
|
|
| 324 |
It should be always possible to use B<boincdir> variable instead - in such case |
|
| 325 |
the file gui_rpc_auth.cfg is read by boinccmd binary directly. |
|
| 326 |
If this plugin is used to fetch data from remote system, the gui_rpc_auth.cfg |
|
| 327 |
can be copied to special directory in a secure way (e.g. via scp) and properly |
|
| 328 | 328 |
protected by file permissions. |
| 329 | 329 |
|
| 330 | 330 |
=head1 INTERPRETATION |
| 331 | 331 |
|
| 332 |
This plugin shows the number of currently running BOINC tasks on the machine.
|
|
| 333 |
If machine is attached to several BOINC projects, data for all these projects
|
|
| 332 |
This plugin shows the number of currently running BOINC tasks on the machine. |
|
| 333 |
If machine is attached to several BOINC projects, data for all these projects |
|
| 334 | 334 |
are displayed. |
| 335 | 335 |
|
| 336 | 336 |
=head1 EXAMPLES |
| 337 | 337 |
|
| 338 | 338 |
=head2 Local BOINC Example |
| 339 | 339 |
|
| 340 |
BOINC is running on local machine. The BOINC binaries are installed in
|
|
| 340 |
BOINC is running on local machine. The BOINC binaries are installed in |
|
| 341 | 341 |
F</opt/boinc/custom-6.10.1/>, the BOINC is running in directory |
| 342 |
F</usr/local/boinc/> under username boinc, group boinc and the password is used
|
|
| 342 |
F</usr/local/boinc/> under username boinc, group boinc and the password is used |
|
| 343 | 343 |
to protect access to BOINC: |
| 344 | 344 |
|
| 345 | 345 |
[boinc_*] |
| ... | ... | |
| 349 | 349 |
|
| 350 | 350 |
=head2 Remote BOINC Example |
| 351 | 351 |
|
| 352 |
BOINC is running on 2 remote machines C<foo> and C<bar>.
|
|
| 353 |
On the local machine the binary of command-line interface is installed in
|
|
| 352 |
BOINC is running on 2 remote machines C<foo> and C<bar>. |
|
| 353 |
On the local machine the binary of command-line interface is installed in |
|
| 354 | 354 |
directory F</usr/local/bin/>. |
| 355 |
The BOINC password used on the remote machine C<foo> is stored in file
|
|
| 355 |
The BOINC password used on the remote machine C<foo> is stored in file |
|
| 356 | 356 |
F</etc/munin/boinc/foo/gui_rpc_auth.cfg>. |
| 357 |
The BOINC password used on the remote machine C<bar> is stored in file
|
|
| 357 |
The BOINC password used on the remote machine C<bar> is stored in file |
|
| 358 | 358 |
F</etc/munin/boinc/bar/gui_rpc_auth.cfg>. |
| 359 |
These files are owned and readable by root, readable by group munin and not
|
|
| 360 |
readable by others.
|
|
| 361 |
There are 2 symbolic links to this plugin created in the munin plugins
|
|
| 362 |
directory (usually F</etc/munin/plugins/>): F<boincprojs_foo> and
|
|
| 359 |
These files are owned and readable by root, readable by group munin and not |
|
| 360 |
readable by others. |
|
| 361 |
There are 2 symbolic links to this plugin created in the munin plugins |
|
| 362 |
directory (usually F</etc/munin/plugins/>): F<boincprojs_foo> and |
|
| 363 | 363 |
F<boincprojs_bar> |
| 364 | 364 |
|
| 365 | 365 |
[boincprojs_foo] |
| ... | ... | |
| 379 | 379 |
|
| 380 | 380 |
=head1 BUGS |
| 381 | 381 |
|
| 382 |
There is no C<autoconf> capability at the moment. This is due to the fact, that
|
|
| 383 |
BOINC installations may vary over different systems, sometimes using default
|
|
| 384 |
directory from distribution (e.g. F</var/lib/boinc/> in Debian or Ubuntu), but
|
|
| 382 |
There is no C<autoconf> capability at the moment. This is due to the fact, that |
|
| 383 |
BOINC installations may vary over different systems, sometimes using default |
|
| 384 |
directory from distribution (e.g. F</var/lib/boinc/> in Debian or Ubuntu), but |
|
| 385 | 385 |
often running in user directories or in other separate directories. |
| 386 |
Also the user-ID under which BOINC runs often differs.
|
|
| 387 |
Under these circumstances the C<autoconf> would be either lame or too
|
|
| 386 |
Also the user-ID under which BOINC runs often differs. |
|
| 387 |
Under these circumstances the C<autoconf> would be either lame or too |
|
| 388 | 388 |
complicated. |
| 389 | 389 |
|
| 390 | 390 |
=head1 AUTHOR |
Formats disponibles : Unified diff