Low: nfsserver: only set rquotad options when port is set
Low: ethmonitor: Perform first monitor during start action

This is mostly an optimization, however it does help indicate
quickly if there are any issues with setting the monitor's
transient attribute in the cib (which is the only failure
condition in this agent)
Low: ethmonitor: Increase recommended default timeout settings

Ethmonitor is designed so the actual resource-agent does not
fail. Instead the failure of a ethernet device is detected
through a transient attribute the ethmontior resource sets.

By default, the timeout values recommended by this agent
will result in Pacemaker (or another cluster manager) timing
out the executing of this agent. The agent itself blocks
attempting to determine the device's status. The default blocking
time is longer than the default recommended timeout. This causes
the ethernet monitoring to fail.
Low: ethmonitor: Use consistent formatting
Low: ethmonitor: Improve logging during monitor operation to help determine reason for failure
Low: ethmonitor: Add pcs example with crmsh example in metadata
Merge pull request #467 from davidvossel/ethmonitor-fixes

minor ethmonitor cleanup
Medium: Xinetd: refine exit codes when xinetd is stopped

Spotted by @bubble666:

https://github.com/ClusterLabs/resource-agents/commit/e9c03c15bdfa49a6bfce784ab922dd0ece546561#commitcomment-4983265
Merge pull request #475 from davidvossel/exit-msg

exit reason string fixes along support for nfs/ip/virtdomain resources.
Merge pull request #480 from dmuhamedagic/xinetd-err_installed

Medium: Xinetd: refine exit codes when xinetd is stopped
Merge pull request #460 from davidvossel/nfs-cleanup

more minor nfs related fixes
High: Filesystem: when loading kernel modules wait for filesystem to initialize

When the Filesystem agent is managing a filesystem type that
is not present in /proc/filesystems, the agent attempts to
load the kernel module for that filesystem.

This patch improves on that logic by
1. verifying that modprobe worked
2. give the module a brief period of time to initialize.

Item 2 is important because there is a brief period
of time between when modprobe returns loading the gfs2
module, and when gfs2 will show up in the /proc/filesystems
list.  Without retrying the search of the /proc/filesystems
file, a gfs2 filesystem may fail to start correctly because
it will look like the filesystem isn't supported.
Merge pull request #478 from davidvossel/bz1083231-fs-mod-load-fix

High: Filesystem: when loading kernel modules wait for filesystem to initialize