Re: update.conf

[Mark . Burgess]

On  4 Apr, Richard Arends wrote:
> Hello,
> 
> I'm working out a cfengine solution for the company i work for. This is
> what i have in mind.
> 
> * cfengine server (run cfservd)
>       On the server several cf files (cf.users, cf.runscripts) And for
>       every host a directory (host1.domain.com) which beholds cf scripts for
>       that host only.
> 
> * update.conf for hosts (clients)
>       From cron every half hour cfagent -f update.conf. Clients gets the 
> common
>       cf files and his own cf files from his own directory on the
>       server.
> 
>       After running update.conf, the common cf files and the hosts own
>       cf file(s) must be executed. The problem here is, that i don't
>       want a static 'import' list, thus when a update.conf has ran i
>       should 'see' what cf files are present and run these.
> 

As a principle of security, you don't want to include just any file you
happen to find there, but you might want to include only certain files
on certain hosts. To do this, just label them with classes:

 import:

   solaris::

      cf.solaris

  hpux|linux::

      cf.xxx

  myclass::

      cf.extras

You can define classes with, f.eks.

classes:

 myclass = ( IfExists(filename) )

or whatever.




Mark