Rainer Gerhards a écrit :
[...]
>
> I have now reviewed the code. My initial posting was correct, rsyslog works
> as intended. While immark generates mark messages at fixed intervals, the
> action processor removes them if the action was recently enough called (see
> action.c, ln. 1189, current master branch). This handling is so that a local
> perception of "recently called" is kept on a per-action basis. This stems
> back to sysklogd, but I also think it is the correct way to handle the
> situation. As such, it is not important if any *other* action was called
> within that interval, it is only important if the action itself was called
> (or not) within the interval.
>
> I would probably fairly easy to add an option to *always* write mark messages
> if there is a real need for such. As of rsyslog policies, that will probably
> only go into v5 (maybe v4, but definitely not v3).
>
> Please let me know your thoughts.
Hi,
Thank you for your reply.
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.
Regards.
--
==============================================
| FRÉDÉRIC MASSOT |
| http://www.juliana-multimedia.com |
| mailto:frede...@juliana-multimedia.com |
===========================Debian=GNU/Linux===
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
