RE: Querying clients

[Martin, Jason H]

One oftentimes has to know which hosts will be impacted by a particular
change so that the appropriate change request tickets can be filed,
support groups notified, potential outages scheduled, and so on. This
can oftentimes be done using ALERTS, but someimtes it is useful to be
able to look at that kind of data w/o having to write a particular class
and wait for the next CFE run. 

-Jason Martin


> -----Original Message-----
> From: 
> help-cfengine-bounces+jason.h.martin=cingular.com@gnu.org 
> [mailto:help-cfengine-bounces+jason.h.martin=cingular.com@gnu.
> org] On Behalf Of Matthew Palmer
> Sent: Thursday, December 08, 2005 4:36 PM
> To: help-cfengine@gnu.org
> Subject: Re: Querying clients
> 
> 
> On Fri, Dec 09, 2005 at 12:43:04PM +1300, Steve Wray wrote:
> > It is still useful to be able to collect data on the 
> existing state of 
> > a
> > machine and pass that back to the cfengine server. I can 
> think of *lots* 
> > of reasons one might want to do this.
> 
> Please share.  I can't think of anything that cfengine can do 
> on the server that it can't do on the client.
> 
> - Matt
> 
> 
> _______________________________________________
> Help-cfengine mailing list
> Help-cfengine@gnu.org 
> http://lists.gnu.org/mailman/listinfo/help-> cfengine
>