From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Whitehouse Date: Mon, 01 Dec 2008 15:34:03 +0000 Subject: [Cluster-devel] Re: Groupd uevent clean up In-Reply-To: <20081201152817.GC24608@redhat.com> References: <1227622122.9571.99.camel@quoit> <20081125154720.GA24769@redhat.com> <1227631472.9571.110.camel@quoit> <20081125170820.GA26746@redhat.com> <1227870476.9571.237.camel@quoit> <20081201152817.GC24608@redhat.com> Message-ID: <1228145643.9571.273.camel@quoit> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, On Mon, 2008-12-01 at 09:28 -0600, David Teigland wrote: > On Fri, Nov 28, 2008 at 11:07:56AM +0000, Steven Whitehouse wrote: > > LOCKTABLE= > > 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= > > 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 > We also need to change groupd and the reason that I didn't resend that original patch is that with these new bits of information, it might be better to implement something a bit more generic, so that it picks up all the right bits of information. Shouldn't be too tricky to keep it backwards compatible either, Steve.