Patch available, will be in 2.1.14 On Fri, 2005-04-01 at 16:14 -0500, Eric Dorland wrote: > On Wed, 2005-03-30 at 15:02 -0500, Eric Dorland wrote: > > On Wed, 2005-03-30 at 18:32 +0200, Mark Burgess wrote: > > > 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: > > > > > > > > > > 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... > > > > > > > Thanks again Mark! That did the trick. You genius is surpassed only by > > your beauty :P Ok, here comes the next question/problem. > > I spoke too soon. Alerts do not get evaluated in the update phase, only > in the main phase. So if I set a class in update.conf to trigger the > alert, it doesn't get run because the main phase has wiped out my > classes. > > Perhaps alerts defined in update.conf should be run before the main > phase? This is the behaviour you seemed to imply from your example. > >
_______________________________________________ Help-cfengine mailing list Help-cfengine@gnu.org http://lists.gnu.org/mailman/listinfo/help-cfengine
