[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
actionsequence suggestion
From: |
Ed Brown |
Subject: |
actionsequence suggestion |
Date: |
Thu, 06 Jan 2005 10:53:38 -0700 |
The limitations imposed by the present actionsequence definition format
is a frequent source of frustration when working with cfengine. Very
often, you want finer control over individual instances of particular
actions, and having to define a qualified instance of the action is not
very scalable or flexible. I'd like to suggest a different approach,
that could coexist with the current implementation, so as not to create
a backwards compatibility problem.
Borrowing from the scheme used for ordering startup/shutdown actions in
the rc.x directories, suppose that cfengine defined internal classes
00->99, that were used only to provide a sort order for actions. So
that you could do something like this:
copy:
25::
/foo dest=/foo ...
60::
/bar dest=/bar ...
editfiles:
{ /foo AppendIfNoSuchLine "Hello" }
70::
{ /foo AppendIfNoSuchLine "Hello" }
The numeric priority for actions without an explicit sequence specifier
default to 50, so the above results in:
copy foo, edit foo, copy bar, edit bar
The actionsequence for actions with the same priority would be
determined as it is now, in the 'control:' section definition, or, if no
actionsequnce is defined in 'control:', it could be left indeterminate
(like rc.x startup actions with the same number)
Any thoughts on this?
-Ed
- Order of Execution, Brian E. Seppanen, 2005/01/05
- Re: Order of Execution, Pau Capdevila/Upcnet, 2005/01/05
- Re: Order of Execution, Brendan Strejcek, 2005/01/05
- Re: Order of Execution, Christian Pearce, 2005/01/05
- Actionsequence as a top level section, Chip Seraphine, 2005/01/05
- actionsequence suggestion,
Ed Brown <=
- Re: actionsequence suggestion, Mark . Burgess, 2005/01/06
- Re: actionsequence suggestion, Tim Nelson, 2005/01/10
- Re: actionsequence suggestion, Brendan Strejcek, 2005/01/10
- Re: actionsequence suggestion, Ed Brown, 2005/01/10
- Re: actionsequence suggestion, John Borwick, 2005/01/10
- Re: actionsequence suggestion, Ed Brown, 2005/01/10
- Re: actionsequence suggestion, Tim Nelson, 2005/01/10
- Parrot, cfengine, and embedded languages, David Douthitt, 2005/01/11
- Re: Parrot, cfengine, and embedded languages, Mark . Burgess, 2005/01/11
- Re: Parrot, cfengine, and embedded languages, Pe5kyTac0, 2005/01/11