From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Peterson Date: Tue, 20 Jun 2006 13:56:27 -0500 Subject: [Cluster-devel] cluster/group/daemon cman.c cpg.c gd_internal. ... In-Reply-To: <20060620180914.11020.qmail@sourceware.org> References: <20060620180914.11020.qmail@sourceware.org> Message-ID: <449844DB.8040700@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit teigland at sourceware.org wrote: > Moving the cluster infrastructure to userland introduced a new problem > that we didn't need to worry about before. All cluster state now exists > in userland processes which can go away and then come back like new, i.e. > unaware of the previous state. Hi Dave, You know this new development cman stuff and I really don't, but I was just thinking: If we used a shared memory segment, we could hold state information there and then cman would remember the cluster state after process termination and restart, possibly making this whole thing unnecessary. Just a thought. Of course, one could also argue that if the process terminated, can we really trust the state information it had at the time? Bob Peterson Red Hat Cluster Suite