From: Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de>
Subject: Re: svlogd as a heavy-duty logger
Date: Thu, 19 May 2005 00:21:17 +0200 [thread overview]
Message-ID: <877jhwjhuq.fsf@kosh.bigo.ensc.de> (raw)
In-Reply-To: <428ACC2E.5090000@gmail.com> (Dean Hall's message of "Wed, 18 May 2005 01:01:12 -0400")
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
deanpence@gmail.com (Dean Hall) writes:
> I work for a company that has a dire need for a syslog replacement, and
> as a long-time daemontools and runit user, I'd like to propose a svlogd
> (or similar) solution for us.
>
> The main reservation I have is the robustness/scalability of svlogd.
> ...
> Has anyone load-tested svlogd, or does anyone have experience with
> svlogd's behavior under a heavy load?
I played some time with svlogd in an environment (Linux-VServer) where
multiple svlogd daemons (>20) run on the same machine. But this solution
showed too bloated because svlogd is too minimalistic and does not support
basic functions:
* encryption of logstream is possible by an external program only which
must be spawned at each logrotation; because of SSL key exchange this
is a very heavyweight operation
* logrotation is very unflexible; low-volume logs will be transmitted very
seldom and svlogd does not support a way to rotate them periodically. You
will need external programs started e.g. by cronjobs which send SIGALRM
to svlogd. But this will have bad sideeffects as it rotates all logfiles
but not only the low-volume ones.
At the end, I switched to syslog-ng. It offers more flexibility and is
more lightweighted.
Enrico
[-- Attachment #2: Type: application/pgp-signature, Size: 480 bytes --]
next prev parent reply other threads:[~2005-05-18 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 5:01 Dean Hall
2005-05-18 22:21 ` Enrico Scholz [this message]
2005-05-19 6:28 ` Gerrit Pape
2005-05-19 12:30 ` Dean Hall
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=877jhwjhuq.fsf@kosh.bigo.ensc.de \
--to=enrico.scholz@informatik.tu-chemnitz.de \
/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;
as well as URLs for NNTP newsgroup(s).