Medium: exportfs: Make unlock_on_stop_default=1 (bnc#864263)

The resource agent should really release all locks which the NFS server
holds when stopping the resource. When this option was introduced, the
default was kept as 0 for compatibility reasons with legacy kernels,
existing users and non-Linux systems.

This is a proposal to make 1 the default. In most cases, this is the
desired behavior, and not setting this option can lead to unexpected
failures.

Original changeset that introduced this parameter: 612559c9
Low: exportfs: Note caveats for unlock_on_stop in longdesc

Add note on limitations of unlock_on_stop on systems where
/proc/fs/nfsd/unlock_filesystem is not available.
Low: exportfs: Improved longdesc for unlock_on_stop
High: CTDB: do not fail monitor operation when ctdb socket does not exist

When starting CTDB with a custom socket location for the first
time, pacemaker's probe operation (monitor_0) fails because
the custom socket does not exist. This patch detects this failure
and returns "not running" instead of a "generic error" return code.
Low: VirtualDomain: cache domain emulator after start

If libvirt goes down, we want to continue to be able to
monitor the domain. We can do this by looking at the domain's
emulator process. Typically we can get this emulator from the
domain's configuration file, but it is possible that the
configuration file will not have an emulator specified. In this
case libvirt uses whatever the default emulator is. To reliably
be able to monitor domains after libvirt goes down, we need to cache
the emulator path in a temporary file so we can retrieve it later.
Low: VirtualDomain: set crm timeout default so this agent can work outside of pacemaker

We have to set the undocumented OCF_RESKEY_CRM_meta_timeout variable
to test VirtualDomain outside of pacemaker. This patch sets a default
timeout variable so the agent will at least work without that value
being specified. Otherwise stop will fail.
Low: VirtualDomain: Suppress error output when running without pacemaker or libvirtd

We should be able to successfully monitor a resource without
libvirtd or pacemaker being available. This patch suppresses
a bunch of error messages that make the monitor's 'exit 0' success
look a bit confusing.
Merge pull request #397 from davidvossel/ctdb_fixes

High: CTDB: do not fail monitor operation when ctdb socket does not exist
Merge pull request #395 from davidvossel/virtdomain-wo-libvirt

More fixes for monitoring VirtualDomain without libvirtd
Merge pull request #394 from krig/unlock_by_default

Medium: exportfs: Make unlock_on_stop_default=1 (bnc#864263)
Medium: mysql: Update mysql with more sensible defaults

The default values used by the mysql RA are outdated. This
patch updates the socket and binary options to more sensible
defaults.

Don't try to use mysqld_safe by default as it performs its own
monitoring and restarting of mysqld which interferes with Pacemaker.
Also look in more places for the mysqld binary as for example
Red Hat-based distributions put the binary in /usr/libexec, not in
$PATH.