From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] waiting in init.d/cman
Date: Wed, 5 Aug 2009 13:20:54 -0500 [thread overview]
Message-ID: <20090805182054.GC17292@redhat.com> (raw)
In-Reply-To: <1249493154.23450.119.camel@cerberus.int.fabbione.net>
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
next prev parent reply other threads:[~2009-08-05 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 16:12 [Cluster-devel] waiting in init.d/cman David Teigland
2009-08-05 17:25 ` Fabio M. Di Nitto
2009-08-05 18:20 ` David Teigland [this message]
2009-08-05 19:32 ` Fabio M. Di Nitto
2009-08-05 19:43 ` Bob Peterson
2009-08-06 16:05 ` David Teigland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090805182054.GC17292@redhat.com \
--to=teigland@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).