On Thu, 2009-08-20 at 12:15 +0200, Frédéric Massot wrote: > To use the watchdog package and the settings "file" and "change" it is > really important that the marks are written every 20 minutes. > > And as we are in a context of a server restart automatically in case of > problems, I think the marks must always be written. That way if the > server is restarted because of an unwritten marks is that there was > really a problem and not a decision of rsyslog. :o) > > It's really interesting to use the watchdog package to have an option to > have the marks are always written.
I have added a new config option $ActionWriteAllMarkMessages, which must be specified in front of the action that needs to write all mark messages (in your case probably all). As of rsyslog policies, this goes into the current development version, which is v5. However, I think the patch should be fairly easy to backport, or even apply literaly to older versions (but I have not tried this and will usually not offer any support for such endavours). http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=c7f746d8349b395b95b3aa70eb395afb07b9c4c7 >From the new doc: ========== <li><b>$ActionWriteAllMarkMessages</b> [on/<b>off</b>]- [available since 5.1.5] - normally, mark messages are written to actions only if the action was not recently executed (by default, recently means within the past 20 minutes). If this setting is switched to "on", mark messages are always sent to actions, no matter how recently they have been executed. In this mode, mark messages can be used as a kind of heartbeat. Note that this option auto-resets to "off", so if you intend to use it with multiple actions, it must be specified in front off <b>all</b> selector lines that should provide this functionality. ========== I did only a quick test, but as this is fairly simple, I do not expect something goes wrong. Any feedback is appreciated. I hope this is useful. Rainer -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
