[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: conf repository?

From: Andrews, Martin
Subject: RE: conf repository?
Date: Sun, 29 Jul 2001 16:38:38 -0400


I have been wondering about ways to piece together modules too. Beyond a set
of rules I think a preprocessor could really help here - it could provide a
standard notation to pass information back and forth and could add prefixes
to classes and macros internal to the modules to avoid naming collisions.
Call it cfengine++. Does that make sense to anyone else? I am still totally
in the brainstorming phase.

Martin Andrews

-----Original Message-----
From: Mark R. Lindsey []
Sent: Wednesday, July 18, 2001 8:33 AM
To: David Fogarty
Subject: Re: conf repository?

On Tue, 17 Jul 2001, David Fogarty wrote:

> Is there a repository of conf files tuned for each service?  It'd be nice
> to be able to grab a cf.OpenSSH, cf.ncftpd, etc. from somewhere.  I'm sure
> there's tons of duplicate conf files out there.  I know I'd be willing to
> share.

I'm not so sure that they're all duplicates -- our configuration framework
here, called "confucius", is built on cfengine, and provides a set of
hooks for phases of the configuration of each element. E.g., our
"shellcommands:configure_services.SshServer" commands enable the 
ssh server on the local machine for SshServer members, and 
"shellcommands:configure_services.!SshServer" disables it for machines
that are not ssh servers.

Further, I haven't found a way to communicate between modules, so we have
local standard macro names. Similarly, the macro pair
$(internal_network_number) and $(internal_nework_netmask) defines the
network which is allowed to ssh in to this machine. (The SshServer module
configures IP filtering.)

I think you're asking for a good thing, but we'd also need to work out
some rules by which these configuration files can play in order to make it

Mark R. Lindsey,, +1-229-241-7378x200 

Help-cfengine mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]