On 04/30/2012 10:54 AM, Abid Khwaja wrote:
> Thanks for the clarification. I tested by commenting out the cf-serverd
> lines in failsafe and cf-serverd did not start. My understanding from the
> CF3 Reference Manual was that failsafe is read only if the main policy files
> cannot be read/parse
On Mon, Apr 30, 2012 at 8:54 AM, Abid Khwaja wrote:
>
> My understanding from the CF3 Reference Manual was that failsafe is read only
> if the main policy files cannot be read/parsed.
Hi, Abid.
That is the purpose of failsafe.cf, you are correct. However, in
version 3.2.1 (I haven't played wit
On Apr 30, 2012, at 3:19 PM, Nick Anderson wrote:
> As far as how to stop it from happening I suspect that cf-serverd is
> being started during your update/failsafe. Look in your body executor
> control. What is the exec_command? I suspect its something like
> "$(sys.cf_twin) -f failsafe.cf && $(s
On 04/30/2012 12:58 AM, Abid Khwaja wrote:
> I have a client CF3 host (cfengine 3.2.3) that is running the policy below.
> When I run "cf-execd --no-fork”, I see that 2 additional processes are
> started: cf-monitord & cf-serverd. Shouldn’t cf-serverd only run the the
> CF3 master host? Ther
I have a client CF3 host (cfengine 3.2.3) that is running the policy below.
When I run "cf-execd --no-fork”, I see that 2 additional processes are started:
cf-monitord & cf-serverd. Shouldn’t cf-serverd only run the the CF3 master
host? There is nothing in this policy that would tell the cli
