[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [SPAM] - Actionsequence as a top level section - Bayesian Filter det
RE: [SPAM] - Actionsequence as a top level section - Bayesian Filter detected spam
Wed, 5 Jan 2005 16:03:07 -0500
I would be happy with this:
actionsequence = (
using the "any" class to define the order would fit in with the current
cfengine model would it not (since any if defined anyways)
From: Chip Seraphine [mailto:address@hidden
Sent: Wednesday, January 05, 2005 12:55 PM
To: Christian Pearce; Cfengine Mailing List Help
Subject: [SPAM] - Actionsequence as a top level section - Bayesian
Filter detected spam
I personally am hoping for an actionsequence: *section*, instead of a
list variable. One that has *all* other sections in it, rather than
just some but not others (e.g. import:, groups:, control:, alerts:,
filters: don't go in there). It might be a little more typing but would
greatly ease order-of-operations issues.
chicago_office:: #Determined in "groups"
import.first #All imported files have their own actionsequence:
Something like the above would make about 75% of my migraine headaches
go away :)
Christian Pearce wrote:
>I believe is talked about once every three months. I suppose the best
>way to handle this is to create scope for the actionsequence. Everytime
>a new actionsequence is reached it gets push onto a stack of some sort.
>Once that particular cfengine script is done executing. Then the
>original actionsequence takes over.
>The other way would be to change it for the rest of the execution.
>Which I can't see being useful. If anything you might want to localize
>the sequence for a particular script.
>I know Mark went ahead and added the second pass of execution to
>cfengine. I believe my script takes advantage of this.
>Add this to the cfwiki.org wishlist. Maybe in the next year someone
>will be interested in developing scope. Then again I could be totally
>wrong. If my time frees up I would certainly entertain taking this on.
>Then again I am interested in what Mark has to say about this.
>Considering it might upset some of the cfengine core principles. To me
>this would be a much better way to handle this. Considering how many
>people want to do this.
>actionsequence = ( shellcommands.firstpass shellcomands
>Any they only want the class firstpass to be valid during the execution
>of shellcommands. Maybe this scoping would help.
>On Wed, 2005-01-05 at 12:00, Pau Capdevila/Upcnet wrote:
>>In a modularized set of scripts (main and imports).
>>Is it possible to redefine the action sequence in an imported script?
>>It is misleading that many things of the main script apply but not the
>>order defined in a inner control section.
>>If not it would be a nice feature to see implemented if possible.
>>on Wed, 05 Jan 2005 08:34:18 -050 Christian Pearce
>>"Brian E. Seppanen"
>>Re: Order of Execution
>>Maybe this will work. This isn't code complete.
>> actionsequence = ( copy shellcommands
>> [Code to copy file to /tmp/a]
>> echo "How are you today?" >> /tmp/a
>> echo "Hello World" > /tmp/a
>>Help-cfengine mailing list
Help-cfengine mailing list
|[Prev in Thread]
||[Next in Thread]|
- RE: [SPAM] - Actionsequence as a top level section - Bayesian Filter detected spam,
Nielsen, Steve <=