From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: Groupd uevent clean up
Date: Mon, 1 Dec 2008 09:28:17 -0600 [thread overview]
Message-ID: <20081201152817.GC24608@redhat.com> (raw)
In-Reply-To: <1227870476.9571.237.camel@quoit>
On Fri, Nov 28, 2008 at 11:07:56AM +0000, Steven Whitehouse wrote:
> LOCKTABLE=<clustername:fsname>
> LOCKPROTO=[lock_dlm|lock_nolock]
>
> to avoid all the messy parsing of the initial event string. Also I've
> added come further information to the two "change" events, so that we
> now have:
>
> FIRSTMOUNT=Done
>
> when the first mounter has finished and:
>
> JID=<journal_id>
> RECOVERY=[Done|Failed]
>
> when recovery has finished. Is there anything else that is useful I
> wonder, while I'm adding new items here? I think I've covered the
> important bits anyway.
That's excellent, much better than the sysfs files. We'll need to keep
the sysfs files around for a while, though, so we don't break the
user/kernel interface.
Dave
next prev parent reply other threads:[~2008-12-01 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 14:08 [Cluster-devel] Groupd uevent clean up Steven Whitehouse
2008-11-25 15:47 ` [Cluster-devel] " David Teigland
2008-11-25 16:44 ` Steven Whitehouse
2008-11-25 17:08 ` David Teigland
2008-11-28 11:07 ` Steven Whitehouse
2008-12-01 15:28 ` David Teigland [this message]
2008-12-01 15:34 ` Steven Whitehouse
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=20081201152817.GC24608@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).