| 1 |
Mick <michaelkintzios@×××××.com> writes: |
| 2 |
|
| 3 |
> Perhaps rsyslog? |
| 4 |
> |
| 5 |
> http://www.rsyslog.com |
| 6 |
> ======================================== |
| 7 |
> "Among others, it offers support for on-demand disk buffering, reliable |
| 8 |
> syslog over TCP, SSL, TLS and RELP, writing to databases (MySQL, PostgreSQL, |
| 9 |
> Oracle, and many more), email alerting, fully configurable output formats |
| 10 |
> (including high-precision timestamps), the ability to filter on any part of |
| 11 |
> the syslog message, on-the-wire message compression, and the ability to |
| 12 |
> convert text files to syslog. It is a drop-in replacement for stock syslogd |
| 13 |
> and able to work with the same configuration file syntax." |
| 14 |
> ======================================== |
| 15 |
> |
| 16 |
> It's in portage. |
| 17 |
|
| 18 |
And I can say as an rsyslog user...of some mnths, that even if you |
| 19 |
don't need all those refinements, for just basic use it just like |
| 20 |
syslog and doesn't require learning yet another config syntax like |
| 21 |
syslog-ng does. |
Archives