supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Dean Hall <deanpence@gmail.com>
Subject: svlogd as a heavy-duty logger
Date: Wed, 18 May 2005 01:01:12 -0400	[thread overview]
Message-ID: <428ACC2E.5090000@gmail.com> (raw)

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.
Right now at our largest data center we're getting pretty constant log
input from around 40 machines. We're using syslog-ng, and it suffers
from some rather fatal problems when coupled with the traditional
logrotate program. I don't want to reintroduce stability issues with a
different technology, and my experience with svlogd is limited to
running a syslog-ish server with it (and socklog) on my personal,
three-computer network. Has anyone load-tested svlogd, or does anyone
have experience with svlogd's behavior under a heavy load?


d


             reply	other threads:[~2005-05-18  5:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18  5:01 Dean Hall [this message]
2005-05-18 22:21 ` Enrico Scholz
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=428ACC2E.5090000@gmail.com \
    --to=deanpence@gmail.com \
    /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).