Jason Kim wrote: > On Tuesday 11 October 2005 13:29, Martin, Jason H wrote: >> Try putting in an 'alert' stanza that is always true (such as >> FOO|!FOO). Also, cfexecd doesn't send any mail unless the output >> differs from the previous run, so you might have to put in a >> shellcommand that echos something to the previous file to make it >> different then the current file. >> > I use the something like the following to ensure that my sysadmins > get bugged every time something fails. I ran into a problem where > something failed consistently, but only alerted once so it got lost > in the ether... > > alerts: > # Bad configs, error out > bad_configs:: > "Config error [$(date)]: Bad thingy, update aborted."
Could you be a bit more complete? How does "bad_configs" get set? -- David Masterson VMware, Inc. Palo Alto, CA _______________________________________________ Help-cfengine mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-cfengine
