RE: Module variables being set late

[Wheeler, John]

AFAICT this is what the 2nd pass is for. If you must have the module run
before the other stuff in the action sequence, I *think*(1) you can have
all the other items in your action sequence that need to have that
module run dependent on a class defined by that module. Then during the
second pass you should see the actions fire.

(1) I've had little luck *engineering* solutions that utilize this
feature.



> -----Original Message-----
> From: Chip Seraphine [mailto:chip@trdlnk.com]
> Sent: Wednesday, January 07, 2004 11:21 AM
> To: help-cfengine@gnu.org
> Subject: Module variables being set late
> 
> 
> I am running a module at the top of my actionsequence, and it sets a
class
> ("foo").  Foo *is* an AddInstallable class.
> 
> Unfortunately, the module runs only *after* everything else in the
> actionsequence, even though it is the first item on the list.  (I'm
not
> sure,
> but I believe that this is new behavior in 2.1; the problems this
behavior
> is
> causing did not exist prior to that.)  This is causing the "foo" class
to
> not
> be set until too late to do any good.
> 
> I've tried running the module the old-style way (with
> "module:modname.foo"),
> but that did not cause it run a the desired time.
> 
> Any ideas?  Any way I can for the modules to run at the beginning of
the
> first
> passs, which what I really need it to do?
> 
> 
> _______________________________________________
> Help-cfengine mailing list
> Help-cfengine@gnu.org
> http://mail.gnu.org/mailman/listinfo/help-cfengine