Description of problem:
multiple corosync processes can be started, which results in havoc on the local node.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. corosync -f &
2. corosync -f
Second corosync invocation starts, resulting in bad behavior.
Second corosync should not start, instead printing an appropriate error to the logs.
Created attachment 440756 [details]
patch honza submitted to address rfe
Created attachment 440757 [details]
revision 3026 - second part of patch to address problem
$ service cman start
$ cd /etc/corosync; cp corosync.conf.example corosync.conf
$ corosync -f ; echo $?
Mar 9 10:44:18 z4 corosync: [MAIN ] Another Corosync instance is already running.
Behaves as expected, maybe some error message printed would be useful.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.