Maybe it can already be found in the documentation(anyone have a link?),
but I'd be interested to see how else one might structure a "files:"
example like Neil offered for any three particular files. I'm not so
much interested in modularization, as in simplification. I'd like for a
service administrator to be able to easily and concisely write her
particular bits, without having to know about or depend on some local
modular conventions. Can it be done anywhere near as simply, AND as
clearly, as it can now in cf2, e.g.:
files:
/var/log/wtmp m=0644 o=root g=utmp action=create
redhat_ws_3::
/etc/yum.conf.team m=0644 o=root g=root action=fixall
ArchiveClient::
/var/spool/archive/ m=0755 o=root g=root action=create
-Ed
Mark Burgess wrote:
> I tend to agree with you, Christopher, that the first priority is to make
> clear the
> *intentions* behind the configuration -- human understanding (knowledge
> management) is
> often sacrificed for efficiency. We should strike a balance.
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
