August 2010
1 post
Introducing the Pacemaker Master Control Process...
The latest addition to the Pacemaker 1.1 series is a master control process (MCP) and associated init script.
This means that Pacemaker is now started/stopped independently of the messaging layer.
We anticipate that this should result in a simpler and more reliable startup/shutdown procedure when used in combination with Corosync.
Forking inside a multi-threaded process like Corosync causes...