I would rather consider it an inconsistency :) -- although it may be consistent with the internal convergence mechanism. I confess I haven't read thoroughly the section in docs describing the processing sequence. I assumed that ( classes, vars , other ). is the normal sequence so that allt the configs have been written accordingly and work all right so far ( except for the one above when using functions to define new class). The second wrong assumption was that it didnt matter too much the order as the cfengine looks for the class generating promises and run them first. It turned out that it doesn't do that, instead it cycles several times per run to reach convergence, which is all right unless you have defined actions on my_private_class and !my_private_class when you may end up with both actions executed.
Regards, mlz. On Wed, Mar 30, 2011 at 6:14 AM, <no-re...@cfengine.com> wrote: > Forum: Cfengine Help > Subject: Re: errors when defining classes based on built-in functions > Author: phnakarin > Link to topic: https://cfengine.com/forum/read.php?3,21286,21302#msg-21302 > > If you ask me, I'd consider it as a bug. Cfengine should populate test_var > the 2nd time it evaluate vars: stanza. Unluckily, I'm not an SVN user either > so I don't know this one has been reported or already fixed. > > Cheers, > --Nakarin > > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine >
_______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
