Sorry, I meant
bundle edit_line resolvconf
Aleksey Tsalolikhin wrote:
> On Tue, Dec 15, 2009 at 1:02 AM, Mark Burgess wrote:
>> And I should have pointed out that the "bundle resolvconf" etc, belongs in
>> the standard
>> library.
>
> Is this why the below does not work? What do I need to do
You are missing
bundle agent resolvconf
Aleksey Tsalolikhin wrote:
> On Tue, Dec 15, 2009 at 1:02 AM, Mark Burgess wrote:
>> And I should have pointed out that the "bundle resolvconf" etc, belongs in
>> the standard
>> library.
>
> Is this why the below does not work? What do I need to do?
>
On Tue, Dec 15, 2009 at 1:02 AM, Mark Burgess wrote:
>
> And I should have pointed out that the "bundle resolvconf" etc, belongs in
> the standard
> library.
Is this why the below does not work? What do I need to do?
myprompt# cf-agent -f ./resolver.cf
cf3:./resolver.cf:33,18: syntax error, ne
And I should have pointed out that the "bundle resolvconf" etc, belongs in the
standard
library.
Mark Burgess wrote:
> Try something like this...
>
> CF2
> ---
>
> resolve:
>
> "search iu.hio.no cfengine.com"
>
Try something like this...
CF2 ---
resolve:
"search iu.hio.no cfengine.com"
128.39.89.10
158.36.85.10
129.241.1.99
CF3 ---
vars:
Well, alright. It's not making sense yet.
I am working my way through the tutorial now
(http://www.cfengine.org/manuals/cf3-tutorial.pdf). Perhaps I'll find
a working example of iteration there.
It's good you'll have something to make this clearer. I reckon it'll
help a lot.
Aleksey
On Tue,
In the approach given, the file is edited twice - once to add each line.
You have to think "sub-routines". Editing is a bundle of promises itself.
My Christmas bundle will help to make this clearer.
Aleksey Tsalolikhin wrote:
> Dear Brendan,
>
> I tried out your code below, expecting it to c
Dear Brendan,
I tried out your code below, expecting it to create
search example.com
nameserver 192.168.1.1
nameserver 192.168.1.2
but it only created:
search example.com
nameserver 192.168.1.1
I am using cfengine 3.0.2 community edition, and calling the code with
"cf-agent -f resolv.cf".
Currently there is no map() function, but you can get a similar result
using iteration.
body common control {
bundlesequence => { 'example' };
}
bundle agent example {
vars:
any::
'nameserver' slist => { '192.168.1.1', '192.168.1.2' };
'search' string => 'example.com';