Re: monitoring svlogd-produced logfiles

[Alex Efros <powerman@powerman.asdfGroup.com>]

Hi!

There a lot of ways to do what you need and I think you overcomplicate.

If you don't need svlogd writing to disc and wish to redirect it output
to some 'summarize' program, then why not use that program instead of
svlogd in ./log/run? Main svlogd task is reliable _writing_to_disc_!

But you can configure svlogd to duplicate your logs (optionally filtered)
to STDERR (in addition to writing to disc). In degenerate case you even
can configure svlogd to write nothing to disc and send all log lines to
STDERR, but I don't understand why you need svlogd in this case. :)

Then, in ./log/run you redirect svlogd's STDERR to some FIFO file:
    svlogd /var/log/something 2>/var/log/MYFIFO
(you can configure a lot of different svlogd to output into single FIFO)
and setup special service which will fetch data from /var/log/MYFIFO,
summarize it, print colored to /dev/tty12 or everything - ./run example:
    exec my_cool_summarizer <>/var/log/MYFIFO

Only one important note about FIFOs - if your 'my_cool_summarizer'
service will be down and will not read from /var/log/MYFIFO all other
svlogd which write into FIFO will also stop soon (after they fill kernel
buffers) and in turn will stop services which they logging.

-- 
			WBR, Alex.