Re: Strategy for "one-off" tasks

[Mark . Burgess]

The trick is to make the one-off thing convergent.

For instance, one completing the action create a file flag
that shows that it has been done:

classes:

 DoOnceOnly = ( !FileExists(/var/run/cfengine/onceonly) )

shellcommands:

 DoOnceOnly::

   "OnceOnlyScript" define=done

files:

 done::

   /var/run/cfengine/onceonly action=create


You should check the details. It's late here and I have been drinking ;)

M


On 10 Jul, Ferguson, Steve wrote:
> I'm interested in hearing how people are applying cfengine to perform "one
> off" system management tasks.  It's fairly obvious how one would insert a
> new configuration task in on a recurring basis.  But how would you approach
> a task that you only want to execute one time?  I've got a few different
> ideas in mind, but I'd like to hear what other folks have been doing in
> practice before I commit to any one process.
> 
> Steve
> 
> ---------------------------------------------------------------------------
> Steve Ferguson
> gedas USA, Inc.
> Operational Services & Infrastructure
> 3499 Hamlin Road West
> Rochester Hills, MI 48309-3240
> USA
> phone +1-248-754-3844
> fax   +1-248-754-3263
> Web Admin Pager: 1-877-622-8869
> Steve.Ferguson@gedas.com
> http://www.gedasusa.com
> ---------------------------------------------------------------------------
> 
> 
> 
> _______________________________________________
> Help-cfengine mailing list
> Help-cfengine@gnu.org
> http://mail.gnu.org/mailman/listinfo/help-cfengine



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Work: +47 22453272            Email:  Mark.Burgess@iu.hio.no
Fax : +47 22453205            WWW  :  http://www.iu.hio.no/~mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~