On Wed, May 18, 2011 at 7:22 AM, Nicolas Charles
<nicolas.char...@normation.com> wrote:
> On 17/05/2011 16:59, Aleksey Tsalolikhin wrote:
>>
>> On Tue, May 17, 2011 at 5:07 AM, Nicolas Charles
>> <nicolas.char...@normation.com>  wrote:
>>>
>>> On 13/05/2011 09:42, Aleksey Tsalolikhin wrote:
>>>>
>>>> Sorry,  I don't recall seeing this in any of the documentation
>>>> I've read so far, but are my promises supposed to go into
>>>> site.cf?   Is that right?  Sorry, I just haven't seen it mentioned
>>>> anywhere and it seems important, I want to make sure I get
>>>> it right.
>>>>
>>>>
>>>> I've made this little table of what each file is:
>>>>
>>>>
>>>> promises.cf           the default config file.
>>>>                        uses cfengine_stdlib.cf
>>>>                        has site.cf as an input
>>>>
>>>> cfengine_stdlib.cf    library
>>>>
>>>> failsafe.cf           failsafe config - calls update.cf if
>>>>                        promises.cf is bad
>>>>
>>>> update.cf             promises to refresh /var/cfengine/inputs
>>>>                        from /var/cfengine/masterfiles; and
>>>>                        /var/cfengine/bin from /usr/local/sbin/cf-*
>>>>
>>>> site.cf               called by promises.cf.  site-specific
>>>>                        configuration - resolver configuration,
>>>>                        access control, and local promises.
>>>>
>>>>
>>> I usually use site.cf to set classes and variables based on the machines
>>> characteristics, but I don't put any promises in it. It's more like an
>>> configuration file.
>>> Maybe others behave differently
>>
>> So do you put your local promises in promises.cf then, Nicolas?
>>
>> Aleksey
>
> What do you call local promises ?


Promises that you write, as opposed to promises written at cfengine.org
and shipped with Cfengine.

The logical place to put your promises, it seems to me, is in promises.cf --
that's where the body common control is, so it's the only place, isn't it.
you can't have to body common controls.  and it's the starting place,
so you want to put policies where they'll be seen by the sysadmin starting
to look for them.

I guess what confused me is the site.cf "site-specific configuration".
I think it's weird that Cfengine by default will edit /etc/resolv.conf to put
cfengine.com in the search path.  I would think each site would want
to set their own search path.  Anyway, I'm not sure what site.cf is....
or why it is a separate file from promises.cf.

I guess I ADD things to promises.cf and CHANGE things is site.cf.

*scratches head*

Aleksey
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine

Reply via email to