On 28 mrt 2011, at 20:35, Frans Lawaetz wrote: > >> If you set such an abort class does that not prevent any promises from being >> kept? I worry that this might put CF into a state of never working until >> NFS is fixed. >> > I'm ok with cf3 bailing out until NFS (or whatever is blocking the > existing processes) is fixed. A lot of my promises are contingent on > NFS access so I'd rather know about (via reports: or something similar) > cf3 quitting early than have it do incomplete promise fixing on a host > in a degraded state.
Maybe a suggestion. Use a cfagent wrapper script. that is executed by cf-execd. That will check the state of the NFS-mount. If this is oke execute cf-agent else bail out, kill cf-agent processes (if possible) and mail a message. It is not ideal! -- Bas van der Vlies b...@sara.nl _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
