Recent Changes - Search:

Softwares

.

CFEngine-server-and-client-operations

Main.CFEngine-server-and-client-operations History

Hide minor edits - Show changes to output

July 27, 2012, at 09:33 PM by 15.219.201.70 -
Changed lines 13-14 from:
4. Once cf-agent is spawned by the client, it will check the /var/cfengine/masterfiles/policy.cf to check if there are any updates,
if no updates then it will execute the client policies and will exit.
to:
4. Once cf-agent is spawned by the client, it will check the /var/cfengine/masterfiles/policy.cf on the policy server
to check if there are any
updates,if no updates then it will execute the client policies and will exit.
July 27, 2012, at 09:32 PM by 15.219.201.70 -
Changed lines 13-14 from:
4. Once cf-agent is spawned by the client, it will check the /var/cfengine/masterfiles/policy.cf to check if there are any updates, if no updates then it will execute the client policies and will exit.
to:
4. Once cf-agent is spawned by the client, it will check the /var/cfengine/masterfiles/policy.cf to check if there are any updates,
if no updates then it will execute the client policies and will exit.
July 27, 2012, at 09:32 PM by 15.219.201.70 -
Added lines 4-6:
(:table border=1 width=50% bgcolor=yellow cellspacing=0 :)
(:cellnr:)
[@
Added line 8:
Deleted lines 10-12:
(:table border=1 width=50% bgcolor=yellow cellspacing=0 :)
(:cellnr:)
[@
Changed lines 12-13 from:
@]
(:tableend:)
to:
Added line 14:
Added lines 16-18:

@]
(:tableend:)
July 27, 2012, at 09:31 PM by 15.219.201.70 -
Added lines 1-19:
!!CFEngine server and client operations.
(:Google1:)
----
1. Place your policy file into the /var/cfengine/masterfiles directory, then update the promises.cf file accordingly.
2. When policy changes are entered into /var/cfengine/masterfiles, the client will pull them to /var/cfengine/inputs directory.

(:table border=1 width=50% bgcolor=yellow cellspacing=0 :)
(:cellnr:)
[@
3. On the client the cf-execd will start cf-agent process at regular intervals.
@]
(:tableend:)
4. Once cf-agent is spawned by the client, it will check the /var/cfengine/masterfiles/policy.cf to check if there are any updates, if no updates then it will execute the client policies and will exit.
5. If there are any changes, then the client will put them change to /var/cfengine/inputs directory.

(:Googletxt:)


(:Googlemm:)
Edit - History - Print - Recent Changes - Search
Page last modified on July 27, 2012, at 09:33 PM