On Tue, 30 Aug 2005, Ed Brown wrote:
On Mon, 2005-08-29 at 19:34, Tim Nelson wrote:
....
He's adding stuff to the end of the filename. So, for example,
say we want file foo on servers that are both mail servers and web
servers, we get this:
Mark (msa) solution:
.../usr/local/bin/foo.__MailServer.WebServer__
Tim templating solution:
.../MailServer.WebServer/usr/local/bin/foo
Naturally I like mine better, but his solution should work just as
well if that's the way he wanted to do it
I have no problem with Mark doing it "the way he wants to do it", but
these aren't at all equivalent solutions to the question of how to
organize your sources, and he was asking for feedback about his
approach. The first obliges you to individually copy the files (or use
some secondary renaming mechanism), the second allows you to recursively
copy a whole directory tree for 'MailServer' or 'solaris' or
'foo_domain_com' or 'DevelopmentNetwork' or whatever. The first would
quickly lead to some complicated naming conventions, and equally
complicated filters and includes/excludes.
Ok, you're right, I'm wrong :), except that my templating stuff
doesn't things the way you suggest :). The reason I do them separately is
that I might have two files in the .../any/etc directory, one named
sudoers, and one named sudoers-meta. sudoers-meta contains lines like
"mode=440", and can also contain owners and stuff. I don't know if this
is the best way to do things, but I couldn't think of anything better :).
--
Kind Regards,
Tim Nelson
Server Administrator
P: 03 9934 0888
F: 03 9934 0899
E: [EMAIL PROTECTED]
W: www.webalive.biz
WebAlive Technologies
Level 1, Innovation Building
Digital Harbour
1010 La Trobe Street
Docklands Melbourne VIC 3008
This email (including all attachments) is intended solely for the named
addressee. It is confidential and may contain legally privileged information. If
you receive it in error, please let us know by reply email, delete it from your
system and destroy any copies. This email is also subject to copyright. No
part of it should be reproduced, adapted or transmitted without the written
consent of the copyright owner.
Emails may be interfered with, may contain computer viruses or other defects
and may not be successfully replicated on other systems. We give no
warranties in relation to these matters. If you have any doubts about the
authenticity of an email purportedly sent by us, please contact us immediately.
_______________________________________________
Help-cfengine mailing list
Help-cfengine@gnu.org
http://lists.gnu.org/mailman/listinfo/help-cfengine