Re: Force cfengine to exit with warning..

[Tyson Tucker]

You could set up your cfagent.conf file so that it does a sanity check 
before importing your main input files.  I'd use a module to define the 
classes because they are fun.  However, there is nothnig to say you 
can't use the vanilla classes section.  Below, I'm assuming the class 
all_good gets defined in the dot_all_my_tease module. 

control:
 actionsequence = ( module:dot_all_my_tease )
 addinstallable = ( all_good )

import:
 all_good::
   cf.main

alerts:
 !all_good::
   "Somethings afoot."
  



Darrell Fuhriman wrote:

> I would like to be able to force cfengine to die and not do
> anything, if a condition is true.
>
> Specifically, if someone has configured a host to use both NIS
> and LDAP for NSS, I want it spit out a warning and exit, and not
> attempt to do anything until the ambiguity is resolved.
>
> Is there a right way to do this?
>
> Darrell
>
>
> _______________________________________________
> Help-cfengine mailing list
> Help-cfengine@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-cfengine
>  


--
Tyson Tucker
EMSL Computer Support
tyson.tucker@pnl.gov
(509)372-6766


The boot sector ends at byte 445 and won is now spelled backwards.