On Tue, Sep 07, 2010 at 05:17:58PM +0200, Andrew Beekhof wrote: > On Tue, Sep 7, 2010 at 3:36 PM, Ryan O'Hara <[email protected]> wrote: > > On Sat, Sep 04, 2010 at 09:42:28PM +0200, Fabio M. Di NItto wrote: > >> On 09/04/2010 07:23 PM, Steven Dake wrote: > >> > On 09/03/2010 09:33 PM, Fabio M. Di NItto wrote: > >> >> On 09/03/2010 09:13 PM, Ryan O'Hara wrote: > >> >>> > >> >>> Same as Steve's patch to corosync init script. > >> >>> > >> >> > >> >> Can you also consider adding "Provides: corosync" as suggested in the > >> >> thread? > >> >> > >> > > >> > wouldn't openais need a requires? > >> > >> Not in the init script, no. > >> > >> The init script header can declare: "Provides: corosync", that will > >> allow any other package to only Requires: corosync and it would make no > >> difference for the init order if the user decides to start openais instead. > >> > >> Fabio > > > > I'm with Steve on this. Stating that the openais init "provides > > corosync" just seems wrong. > > Makes perfect sense to me given that starting openais also starts corosync. > I'd agree with you if openais just loaded and unloaded plugins into an > already running corosync - but AFAIK it doesn't.
Yes, understood. The patch has been posted. In the near future the openais init script will be scrapped. > > Then again, I don't see what the point of > > even having an openais init script is. At this point, openais should > > just provide AIS services as libraries. Nothing to "init". > > > > Ryan > > > > _______________________________________________ > > Openais mailing list > > [email protected] > > https://lists.linux-foundation.org/mailman/listinfo/openais > > _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
