Re: Executing a file only on later passes

[David J. Bianco]

I'd just like to point out that some of us specifically rely on this
feature.  For example, I routinely do:

copy:
  <some file> dest=/etc/<somefile> define=FILE_UPDATED

shellcommands:
  FILE_UPDATED::
    "/etc/init.d/service restart"

Which has the effect of restarting a service on the second pass if its
config file changes in the first pass.  If this feature were to be
eliminated, in fact, it would break probably 60% of my config files.
Multiple passes are your friends!  In a non-procedural language like
cfengine, they're basically the only way to create complex multi-step
operations.

        David


Mark.Burgess@iu.hio.no wrote:
> John,
>
> yes I am saying that this could break some more convoluted operations
> in cfengine. The feature is there precisely so that none of us has
> to think about the issues of dependencies. 

--
David J. Bianco, GSEC GCUX GCIH         <bianco@jlab.org>
Thomas Jefferson National Accelerator Facility
GPG Fingerprint:  516A B80D AAB3 1617 A340  227A 723B BFBE B395 33BA

     The views expressed herein are solely those of the author and
            not those of SURA/Jefferson Lab or the US DOE.