Dev: include a verbatim copy of LGPL license file
make SQUID_PIDS[2] work for systems with IPv6 as well
High: IPaddr2: make sure that some ARP send program runs

This is a regression fix which got introduced in commit
a5305b91dd1d2199a75f44130d1d963a7e789e8c:

commit a5305b91dd1d2199a75f44130d1d963a7e789e8c
Author: Dejan Muhamedagic <dejan@suse.de>
Date:   Sat Nov 10 20:21:45 2012 +0100

    Medium: IPaddr2: use send_arp instead of ipoibarping if not
	available
Merge pull request #184 from kskmori/add-lgpl-license

Dev: include a verbatim copy of LGPL license file
Modifications to set JAVA_OPTS at the time of su start
Merge pull request #188 from nozawat/ticket2286

Modifications to set JAVA_OPTS at the time of su start
use correct default value for control-binary
Return success if no program could be found for the pid. A warning will be issued though and the pid-file will be removed
LVM agents:  Missing '$' causing variable to not be accessed properly

Typo in earlier patch.

Helps resolve rhbz729812
Merge pull request #193 from jbrassow/master

LVM agents:  Missing '$' causing variable to not be accessed properly
Merge pull request #191 from FSchumacher/no-error-when-no-pound-is-running

pound: No error when stopping pound and no pound is running
Merge pull request #186 from kurtkeller/201301_Squid_fix

make SQUID_PIDS[2] work for systems with IPv6 as well
LVM agents:  Retry VG shutdown to cope with udev collisions

When trying to shutdown a VG, a failure can occur due to udev
opening an LV.  A error with a message similar to the following
can occur:
  lvm[25454]: Can't deactivate volume group "vg1" with 1 open logical volume(s)
Allowing udev to settle and trying the operation again helps to
resolve the issue.

Helps to resolve rhbz729812.
Merge pull request #196 from jbrassow/master

LVM agents: Retry VG shutdown to cope with udev collisions
Medium: nfsserver: fix all cause an error to call rpc.statd
Medium: pound: fix space character
Low: pgsql: support starting as Hot Standby

rep_mode=slave starts PostgreSQL as Hot Standby to connect to Primary.
This mode does not support Master/Slave configuration.
Low: pgsql: add check_wal_receiver parameter

add check_wal_receiver parameter to check wal_receiver process on monitor
and notify its status using "<resource name>-receiver-status" attribute
to check  whether PostgreSQL(Hot Standby) connects to primary.
The attribute shows status as "normal" or "ERROR".
Default is false.
Merge pull request #198 from t-matsuo/start-as-hs3

Start PostgreSQL as Hot Standby and check wal_receiver process
Merge pull request #197 from nozawat/master

Medium: pound: fix space character