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: > [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > org] On Behalf Of Matthew Palmer > Sent: Thursday, December 08, 2005 4:36 PM > To: [email protected] > 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 > [email protected] > http://lists.gnu.org/mailman/listinfo/help-> cfengine > _______________________________________________ Help-cfengine mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-cfengine
