Re: No reliable outputs in 2.1.15 ?

[Jason Kim]

On Tuesday 11 October 2005 14:28, David Masterson wrote:
> 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?

It's just a class that gets set by a module. Sorry, I just chose an example 
from one of my configs. The point was that using $(date) in the string 
guarantees that the output will be different from the last and therefore be 
emailed.
-JayKim