Forum: CFEngine Help
Subject: Re: "any" usebundle
Author: mark
Link to topic: https://cfengine.com/forum/read.php?3,24472,24491#msg-24491
I tried this
bundle agent test
{
methods:
"my famous string" usebundle => test("$(this.promiser)");
}
bundle agent test(params)
{
reports:
cfeng
Forum: CFEngine Help
Subject: Re: Anomoly in files changes => detect_content on NFS mounted data
Author: GFLehr
Link to topic: https://cfengine.com/forum/read.php?3,24414,24490#msg-24490
Nakarin,
Thanks for the suggestions. I have added the 'file_select => plain' and changed
the 'depth_search' t
> Author: sauer
> Link to topic: https://cfengine.com/forum/read.php?3,24472,24485#msg-24485
> I use that value as a descriptive name, the same way other promises use it;
> usually I choose a more descriptive version of the bundle name, but it always
> describes the purpose in one or two words.
Forum: CFEngine Help
Subject: Re: CFEngine Help: Re: if assignment in cfengine
Author: zzamboni
Link to topic: https://cfengine.com/forum/read.php?3,24461,24488#msg-24488
Mark Burgess Wrote:
---
> Simon, with ifvarclass => you can make strings
>
Forum: CFEngine Help
Subject: Re: CFEngine Help: Re: "any" usebundle
Author: sauer
Link to topic: https://cfengine.com/forum/read.php?3,24472,24485#msg-24485
Oace, Tod R Wrote:
---
> I think called bundles should be able to do the
> same thing. A
Simon, with ifvarclass => you can make strings composed
of variables, where with the context:: syntax you can't.
Personally i find
context::
clearer, but the other is more flexible for "fancy" context handling.
M
On 01/05/2012 09:36 AM, Simon Blake wrote:
> On Wed, Jan 04, 2012 at 03:12:1
Forum: CFEngine Help
Subject: Re: if assignment in cfengine
Author: davidlee
Link to topic: https://cfengine.com/forum/read.php?3,24461,24483#msg-24483
Thanks, Simon. I think you're right about my file:/commands: example. I had
simplified it from a generalised library that we have, in which our
On Wed, Jan 04, 2012 at 03:12:17PM +0100, davidlee said:
> commands:
> ### If a file was adjusted above, run a command:
> optional_class::
> "/sbin/service my_service restart"
> ifvarclass => "class_indicating_file_change";
Is there any particular reason to use the above s
