Hey, I really like the idea of copy templating that's presented in that web page. It would eliminate a lot of redundant lines from my cfagent.conf file, and make copy statements a lot easier to read.
I'm not so sure about the Action templating idea though. The problem is this: With a copy statement, using DefaultCopyType = ( checksum ), the file will only be copied if the checksum differs from the master. The checksum is easy to check, because the file should be exactly the same as it is on the master. If you are using Action Templating and some perl code to "customize" each config file for that particular server, now the checksum will never match, and the copy statement will be invoked every single time, causing bandwidth issues, as well as chewing up quite a bit of CPU time invoking perl for every config file on every cfagent run. How do you work around this issue? Great ideas though. Luke -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tim Nelson Sent: Wednesday, May 25, 2005 12:02 AM To: Tod Oace Cc: Alexander Jolk; Cfengine Help Mailing List Subject: Re: server iteration That's why we need Templating in the next version of cfengine: http://cfwiki.org/cfwiki/index.php/Templating_Ideas Warning; the above documents a number of different templating ideas. Naturally, I like the Action Templating one, as that's my idea :). _______________________________________________ Help-cfengine mailing list Help-cfengine@gnu.org http://lists.gnu.org/mailman/listinfo/help-cfengine