On Mon, 28 Apr 2008, Christine Caulfield wrote: > This is a patch that adds some standalone code to libconfdb, so it can > examine and ultimately change, the configuration without aisexec running. > > A small number of things I'm unsure about.. > > - it automatically falls back to standalone if it can't connect to > aisexec. That might not be the right thing to do, opinions welcome. >
How about a connection flag? Example (with really bad names): STANDALONE = fire standalone if aisexec is not running NOSTANDALONE = fail if no connection NOAISEXEC = only if i can run in standalone (for example to convert configs from one format to another, you want to make sure no aisexec is running to avoid interfering with running config...) > - any program accessing confdb needs to be linked -rdynamic so that > several objdb/config symbols can be resolved. There might be ways around > this though I'm not sure how nice they are! Is this always required or only when running in standalone? > - Some config options I haven't got to work yet. In particular the new > cman preconfig module calls logsys, and I'm undecided about the best way > to tackle this. I think maybe the callers ought also to link with > logsys, but a quite test seems to make this difficult for some reason. what's the scenario here? I am not sure i understand it. Fabio -- I'm going to make him an offer he can't refuse. _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
