On Wed, 2005-03-30 at 11:08 -0500, Eric Dorland wrote: > On Tue, 2005-03-29 at 20:55 -0500, nathan r. hruby wrote: > > On Wed, 30 Mar 2005, Tim Nelson wrote: > > > > > On Tue, 29 Mar 2005, Eric Dorland wrote: > > > > > >> Is it possible to define a class in the update.conf that will be carried > > >> over to cfagent.conf? This doesn't seem to be the case right now. > > >> Specifically a define= on a copy command? Would autodefine work in this > > >> case, eg would an autodefine in cfagent.conf pick up on a copy that > > >> happened in the update phase? > > > > > > I can't think of anything non-klugy (ie. make a file in update.conf, > > > and check it in cfagent.conf), but have you considered moving that > > > particular > > > copy to your cfagent.conf (and use actionsequence to put it at the very > > > start)? > > > > > > > Huh. Could you use SetState() to simply define a call that would carry > > over? > > > > http//www.cfengine.org/docs/cfengine-Anomalies.html#Persistent-alerts > > How would I call SetState() in response to successful copy? > > The file creating thing, although klugy, looks promising. > > I've basically got a cf script that installs some firewall rules, and I > only want to reload the firewall rules if the script has actually > changed. So doing the copy within the script would be a bit too late, > since the script is already loaded. >
copy: .... define=success alerts: success:: SetState... _______________________________________________ Help-cfengine mailing list Help-cfengine@gnu.org http://lists.gnu.org/mailman/listinfo/help-cfengine
