From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] syslog-ng Vs rsyslog
Date: Mon, 17 Nov 2008 23:49:31 +0000 [thread overview]
Message-ID: <200811172349.49991.michaelkintzios@gmail.com> (raw)
In-Reply-To: <840653820811161901n12e0c0cdo4174b54b972fd3dc@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 634 bytes --]
On Monday 17 November 2008, ThaUnderDog wrote:
> > Have you experience perhaps of rsyslog and how does it compare with
> > gentoo's default syslog-ng?
>
> The native/internal modules of db writes and alerting of rsyslog sound
> promising. There's a comparison here:
> http://www.rsyslog.com/doc-rsyslog_ng_comparison.html
>
> Portage isn't in sync with rsyslogs development tree yet. Latest in
> v3-stable is 3.20.0, which appears to build OK. I don't know if there
> are any gentoo specific gotchas, not much experience with it
> yet....everything seems fine...
Thanks! Useful link and feedback.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2008-11-17 23:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-15 16:36 [gentoo-user] syslog-ng Vs rsyslog Mick
2008-11-17 3:01 ` ThaUnderDog
2008-11-17 23:49 ` Mick [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200811172349.49991.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox