Jason Edgecombe wrote:
Tracy R Reed wrote:
I am using cfengine 2.1.16 on CentOS 4.3. I have machines on a local
192.168 network and machines with public ip's outside of our local
network. I would like to be able to manage all of the policy from one
place and keep all of the machines consistant both inside and out. It
you can do exactly what you suggest.
here would be a snippet from update.conf:
I put this problem on the back-burner for a week or so but now I am back
at it. We still have a problem. I currently have the following in my
update.conf:
192_168_1::
policyhost = ( sdapp01 )
192_168_2::
policyhost = ( sdapp01 )
192_168_3::
policyhost = ( sdapp01 )
69_43_173::
policyhost = ( mail )
192_168 does not seem to be a class that ever gets defined so I have to
use 192_168_1 etc. I may try defining it myself later with IPRange() but
one thing at a time. An even bigger problem seems to be that only the
hard classes are defined when update.conf is being processed.
Output from an example cfagent -v run can be found here:
http://paste.plone.org/4209
Note that only the hard classes are defined when the update.conf is
processed. Then later it defines all of the soft classes like 192_168_1
etc. I have tried putting a groups: statement in my update.conf and
defining some classes that way hoping I could then make decisions on
them before any policy is loaded but that seems to be getting ignored.
Any recommendations on how to ensure that the proper classes when
update.conf is run?
--
Tracy R Reed
http://ultraviolet.org
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
http://cfengine.org/mailman/listinfo/help-cfengine
