Forum: Cfengine Help Subject: Best practices advice - Cfengine + network file systems Author: jgreer Link to topic: https://cfengine.com/forum/read.php?3,21402,21402#msg-21402
I'm interested in hearing feedback from the development team and community about using Cfengine with network file systems. Here's the specific problem that prompts the request: I'm writing policy that creates directories and files on an NFS share if and only if they do not already exist. While our storage is stable, I want to mitigate the risk of unintended behavior - if the NFS share should become unavailable and cf-agent should run, these files and dirs would be recreated on local disk. I would like to prevent that from happening. I'd like to protect those promises in policy with a class that's enabled based on the NFS share being in a known-good state. I've considered checking for the existence of (and maybe also, the ability to write to/repair on copy) a 'canary' file on the mount, but that strikes me as an ugly hack. I'm interested to hear from others about solving this and broader best practices advice about Cfengine and network file systems. Thanks, -Jessica _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
