Med: Look for "sm-notify" in $PATH.

Useful for eg. RHEL6-compatible distributions; yes, it can be specified,
but if it works "by default" it's still better.
Medium: Raid1: do not test for device existence in the stop operation (bnc#821861)

Sometimes udevd may not react quickly enough and remove the
devices, hence the stop operation may unnecessarily fail. Whether
a device file exists or not is anyway irrelevant when stopping.
Medium: tools: send_arp.libnet: reuse ARP packets (debian#701914)

This is just a reshuffle of code to have the libnet packets
reused instead of creating new ones each time a packet is to be
sent. There are no functional changes, the program should be a
bit faster and require less resources (memory in particular).
High: ip.sh: Fixes usage of ipv6 addresses with uppercase lettering

Resolves: rhbz#895075
High: named.sh: Addition of update-source option.

Resolves: rhbz#680748
Medium: fs-lib.sh: Faster filesystem start/stop through use of 'findmnt' command for 'is_mounted' function

Resolves: rhbz#919231
Resolves: rhbz#851188
HA LVM should only remove missing PVs on stop when they belong to mirrors

This adds --mirrorsonly to the 3 'vgreduce --removemissing' calls in the
LVM agents.

You'll also notice that it adds another self_fence check after we fail to
remove tags.  In my previous comment, I pointed out that in the case of
single-host by_lv, after we vgreduce we then can't deactivate the logical
volume again because it doesn't exist.  This results in us executing
self_fence, which may have just been a happy accident.  But when we avoid
making metadata changes by adding --mirrorsonly, the subsequent deactivation
is still successful, and thus we miss the self_fence logic.  So, I added
another check so we still catch the failure and fence ourselves in this
situation.

J.B - Retain the loop in 'vg_stop_clustered' that waits for udev to settle
      when trying to deactivate the volume group.  Failure to do so can
      lead to failure to deactivate the volume group.

Signed-off-by: John Ruemker <jruemker@redhat.com>
Signed-off-by: Jonthan Brassow <jbrassow@redhat.com>
Medium: Raid1: wait for udevd to settle (bnc#821861)

Sometimes udevd does not create devices as quickly as needed.
This patch introduces a new parameter (udev). If it's set to true
(which is also the default) it will invoke udevadm settle to wait
for udevd to finish creating the MD device. We also use
--exit-if-exists not to wait unnecessarily for other events.
Medium: Raid1: set MDADM_NO_UDEV appropriately if udev is not used
Merge pull request #270 from l-mb/master

Use explicit shell in oracle/oralsnr (bnc#825517)
Medium: Raid1: stop arrays even with block device file missing (bnc#821861)

An MD array may be running, but the device file /dev/mdnn
missing (i.e. due to some udevd issue). This patch enables Raid1
to stop successfully such arrays.
Med: oracledb.sh: Set RESTART_RETRIES back to 0

Restore the previous value of 0 for RESTART_RETRIES as testing
turned up problems when using RESTART_RETRIES=3 and the storage
on which oracle was installed failed.

Signed-off-by: Ryan McCabe <rmccabe@redhat.com>
Merge pull request #271 from ryan-mccabe/master

oracledb.sh: Set RESTART_RETRIES back to 0
Low: pgsql: add a function to retry command
Low: pgsql: change name and specification of exec_func_with_timeout

- change function name from exec_func_with_timeout to exec_with_timeout
- change specification of exec_with_timeout to conform it to exec_with_retry
- exec_with_timeout outputs more logs
- increase in performance
Low: pgsql: Share output of crm_mon. If crm_mon fails, RA re-exec it
Low: pgsql: improve error handling of crm_xxxx commands and reload_conf()

- if crm_xxx command fails, retry executing it
  because the number of IPC connections reaches maximum,
  crm_xxxx commands fail.
- if reload_conf() fails, retry it, because the failure is critical
Low: pgsql: report failed query and return code

- report_psql_error() reports given message to distinguish failed query
  when using replication mode.
- change some loglevels from warn to err when calling report_psql_error(),
  because warn should be used for starting up PostgreSQL.
Low: pgsql: simplify picking out data status
Medium: pgsql: set only one node into sync mode when using 3 nodes or higher

Only one node can be sync mode to avoid data loss when using 3 nodes or higher.
See http://www.gossamer-threads.com/lists/linuxha/pacemaker/85077?do=post_view_threaded#85077