Whitespace cleanup

* remove trailing whitespace
* remove empty lines at the end of files

plugins/boinc/boinc_wus

@@ -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