Low: Core: Bug cov#739430, cov#739431 - Dereference after null check
Low: IPC: Bump the timeout sent to qb_ipcc_recv() for synchronous replies
Low: extras: perl-TimeDate is needed for CTS
Low: Core: Bug cov#739444 - Resource leak
Low: Core: Bug cov#739451 - Insecure temporary file (claimed)
Low: Core: Big cov#739460 - Time of check time of use in crm_lock_pidfile()
Low: Fencing: Bug cov#739425 - Logically dead logging code
Low: Fencing: Bug cov#739426 - Correctly pass back failures to exec agents by internal_stonith_action_execute()
Low: Fencing: Bug cov#739428, cov#739429, cov#739447 - Dereference before null check
High: Fencing: cov#739453 - String not null terminated
Low: Core: Bug cov#739707 - Dereference after null check
Low: cib: Bug cov#739564 - Resource leak
Low: crmd: Bug cov#739459 - Suppress 'time of check time of use' defect
High: mcp: Re-attach to existing pacemaker components when mcp fails
High: fencing: Terminate stonithd when cib connection fails.
Medium: lrmd: Fix removal of old lrmd instances
Merge pull request #172 from davidvossel/mcp_pid_reattach

mcp reattach to pids on failure
High: Remove functionality for terminating old lrmd and pengine instances

If corosync or heartbeat dies, anything with a connection to it will
exit.  The pengine and lrmd are not cluster aware and so would hang
around.

Previously the new instance would arrange for the old to terminate,
however there is little point as the node would normally be fenced.

So don't bother anymore, especially as respawning all the daemons
creates additional downtime when pacemakerd is involved.

(A separate patch allows pacemakerd to 're-attach' to existing daemons
at startiup)
Merge branch 'master' of github.com:ClusterLabs/pacemaker
Low: mcp: Tweak log message