William A. Rowe, Jr. wrote:
Offhand, no, but I'd suggest looking at Piped Log scripts.
This would be pretty trivial to do (even looking for very
specific messages or masking out other common occurances.)
The messages can then be written to one or more log file,
as well.
See the ErrorLog documentation for pipe syntax, and rotatelogs
or logresolve for additional examples.
Another possibility is to, more or less, write a script that does
the same thing as 'tail -f', or alternately a script that runs
periodically and keeps track of the position it left off at in the log.
