> P.S. another example is a network failure that renders part of your > system unreachable - let's say you lose access to 20 servers at a > remote site. When the network service is restored, Cfengine on > the 20 servers will contact the distribution server and download > the policy.
I agree with your examples. Pulling is more reliable in cases of outages. I'm still learing how to use cfengine for my tasks. My question was more about updates during policy development and testing. When I'm testing changes I usually want to see any effects immediatelly and chack that a new policy does what I want. Suppose, cf-runagent is a wrong tool for this. But still. I don't see any means to distinguish multiple cf-serverd instances on a single host. Looks like that server ID contains only IP address in version 3.1.5, neither port number, nor os user name is used for ID. Multiple cf-serverd instances on a host would have the same ID, but different keys. Looks like a missfeature, maybe a minor one. Thanks to all. _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
