So you are quite right that there is more to the story. I dug around in my
bundles and found that there was overlap with respect to this file. A
generic "centos_5" promise included update of limits.conf whereas further
down in the bundle I had a more specific class "centos_5.special_hosts"
which brought in a different limits.conf. This means that with each
cf-agent run the file was updated back and forth.
The above explains greater probability of this bug (assuming there is one)
snaring limits.conf. Were it not for this flip-flop of the file, cf-agent
would have matched the hashes and not attempted an update. That written it
is still problematic that cf-agent was able to corrupt a file. Either
limits.conf (the generic or more targeted) would have been fine but instead
the file went missing.
The last promise is below. It's just a simple file copy as was the prior
promise.
"/etc/security/limits.conf"
copy_from =>
mycopy("${g.masterfiles}/farm/etc/security/limits.conf.crdwga","${g.phost}"),
perms => m("755");
Frans
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
