Thanks for the info, I figured as much as this, just wanted to make sure before scrapping what I was trying to do and rework it.
What I am trying to do is pretty simple in theory. The server contains a flat file of host information about each client that connects. Since I am trying to make a very light footprint during the installation phase of cfengine, this downloaded flat file determines the makeup of the client - support level, system admin, and the like. The support level would determine which configuration to download. If a client has cfengine installed for the first time, the server may not know about it yet. The client would then add itself into the local copy of this flat file and put some default values in it, and run from there. It will notify the system admin that the host is not contained within the server copy of the flat file. But just to get the client up and running with minimal administration, I choose this method. Bascially, install and bootstrap the client, and it is all taken care of. It was been working very well, until I started testing if the host is not within the server copy of the flat file. Being the freak that I am, I must have cfengine deal with all cases of human non-intervention, and add itself in the flat file locally, until a human can determine what should be on the host. This would probably be better configured using classes in the config itself, but I am reducing the configuration to be very modular and clean. Setting classes for each host would complicate the config beyond belief in my environment, and I would not like to have the client have information about every other host in the environment. It is a very large and varied environment, and I am trying make it very readable and easy to configure, with very low overhead. _______________________________________________ Bug-cfengine mailing list [email protected] https://cfengine.org/mailman/listinfo/bug-cfengine
