Logsurfer is a program that works on single textlines from a logfile
(or from standard input). It compares each line against regular
expressions of a set of "rules" and performs certain actions that are
defined for this match.

Log message:
Update to Logsurfer+ 1.7. Changes:
* Added -e option to begin processing from the current end of the input log file.
* Put double-quotes around regex expressions in dump file.
* If the context argument to a pipe or report action is "-" then the \
current context contents are piped into the command.
* Added "echo" action which simply echo's the output on stdout, or to \
a file.
* Added a "$lines" macro construct in context action fields, it will \
be substituted by the number of lines in the context.
* Added "syslog" action to send a message into syslog.

Log message:
Update logsurfer to 1.6.2(1.6b), requested in PR 33892.
ChangeLog:
Version 1.6b (logsurfer+)
+ fixed -t option in getopts()
Version 1.6a (logsurfer+)
Kerry Thompson kerry_at_crypt.gen.nz:
+ corrected off-by-one in min_lines checking
+ added min_lines context arg to logsurfer.conf man page
Version 1.6 (logsurfer+)
Kerry Thompson kerry_at_crypt.gen.nz:
+ added an optional parameter at the end of context definition
(just before action) specifying the minimum number of lines
collected which needs to be satisfied before performing action
+ added -t option to explicity timeout contexts when exiting
default=off so contexts don't all trigger when we shut down
+ only add lines to a context if the context has an action of
'pipe' or 'report'. In other words, don't store lines in
memory which won't ever be used. The number of matching
lines in the context is still incremented. This allows contexts
to be created which can notify if we _don't_ see an event, such
as regular "syslog pings" from hosts.