From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Teigland Date: Wed, 5 Aug 2009 13:20:54 -0500 Subject: [Cluster-devel] waiting in init.d/cman In-Reply-To: <1249493154.23450.119.camel@cerberus.int.fabbione.net> References: <20090805161239.GA17292@redhat.com> <1249493154.23450.119.camel@cerberus.int.fabbione.net> Message-ID: <20090805182054.GC17292@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Wed, Aug 05, 2009 at 07:25:53PM +0200, Fabio M. Di Nitto wrote: > I can see the possibility to block the boot for quorum when quorum might > never be available. As above, I don't mind to add that to the init > script, but it will need yet another timeout. Sure, but as I mentioned, if cman doesn't wait for quorum, then clvmd, rgmanager or gfs mount will... and those don't time out and sometimes can't be cancelled, whereas cman_tool wait -q can be. The no wait option is good, it could make sense in some cases, like when no other init scripts follow cman that depend on quorum. Dave