--On Friday, March 18, 2005 16:40:41 +0100 Mark Burgess <[EMAIL PROTECTED]> wrote:
> .... Please let's > be clear about this, The problems people are hvaing with Berkeley DB are > 99% to do with version management. > > Mark > I agree it's a version management issue, but what is the solution? Chances are the system libdb will get updated at times not always coinciding with cfengine builds, so you either have to maintain a separate set just for cfengine, and ensure that the correct ones are actually linked in at runtime, or you need to link cfengine statically. Even if you do ensure that cfengine is using the correct library, when you build a new version of cfengine with a different Berkeley db library, if the existing .db files can cause a problem executing cfengine, then you are really out of luck, as manually logging in to hundreds (or maybe thousands) of servers to remove them is not practical. Perhaps cfengine could store the db version in the db files and remove (or ignore and warn) if the version has changed, or if it can't extract the version from the file due to a change in internals. Frank -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501 _______________________________________________ Help-cfengine mailing list Help-cfengine@gnu.org http://lists.gnu.org/mailman/listinfo/help-cfengine
