On Wed, Apr 29, 2009 at 02:28:05PM +0200, Andrew Beekhof wrote: > At the moment, startup and shutdown ordering is controlled by the > plugin's position in an objdb list. > > This is particularly problematic for cluster resource managers which > must be unloaded/stopped first. > The reason for this is that they (or the resources they control) need > access to at least some of the other services provided by Corosync. > > Based on input from Steve, this patch resolves the shutdown side of > the equation and if its acceptable I'll work on the startup side of > things.
I wonder if the recent cfg shutdown api from chrissie would be relevant to this? It also brings up the question of whether corosync should have a program to start/stop the corosync daemon? "corosync_tool join" to set a config method and start corosync "corosync_tool leave" to stop corosync if it's not being used by apps (would use the cfg api) Dave _______________________________________________ Openais mailing list Openais@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/openais
