[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Warning: Redefinition of macro
From: |
Mark Burgess |
Subject: |
Re: Warning: Redefinition of macro |
Date: |
Fri, 8 Nov 2002 10:45:17 +0100 (MET) |
On 8 Nov, Adrian Phillips wrote:
>>>>>> "Rune" == Rune Mossige <runemo@stavanger.westerngeco.slb.com> writes:
>
> Rune> We used to have this set in the update.conf control:
> Rune> section, but then the new 2.0.4 clients complained, forcing
>
> You mean the variable wasn't defined ?
>
> Rune> us to also set it in cfagent.conf. Is this behaviour
> Rune> expected?
>
> It seems variables carry over from update.conf - I had to do comment
> out a repeated in cfagent.conf variable when I upgraded.
>
> You could try defining a class based upon the cfengine version as a
> temporary measure :-
>
> cf204 : ( "/bin/sh -c 'cfagent --version | grep -q 2.0.4'" )
>
> then only define the cfagent.conf varable if the class doesn't exist.
>
> Sincerely,
>
> Adrian Phillips
>
The policy was changed in 2.0.4 so that variables are private in
update and cfagent.conf
M