From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/814 Path: news.gmane.org!not-for-mail From: Enrico Scholz Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: svlogd as a heavy-duty logger Date: Thu, 19 May 2005 00:21:17 +0200 Message-ID: <877jhwjhuq.fsf@kosh.bigo.ensc.de> References: <428ACC2E.5090000@gmail.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Trace: sea.gmane.org 1116455299 21038 80.91.229.2 (18 May 2005 22:28:19 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 18 May 2005 22:28:19 +0000 (UTC) Original-X-From: supervision-return-1050-gcsg-supervision=m.gmane.org@list.skarnet.org Thu May 19 00:28:15 2005 Return-path: Original-Received: from antah.skarnet.org ([212.85.147.14]) by ciao.gmane.org with smtp (Exim 4.43) id 1DYWyn-0000x4-M4 for gcsg-supervision@gmane.org; Thu, 19 May 2005 00:25:29 +0200 Original-Received: (qmail 22152 invoked by uid 76); 18 May 2005 22:26:38 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 22146 invoked from network); 18 May 2005 22:26:38 -0000 Original-To: supervision@list.skarnet.org In-Reply-To: <428ACC2E.5090000@gmail.com> (Dean Hall's message of "Wed, 18 May 2005 01:01:12 -0400") User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, linux) X-Provags-ID: kundenserver.de abuse@kundenserver.de login:cf015127439e61eb16a460417aa16ac1 Xref: news.gmane.org gmane.comp.sysutils.supervision.general:814 X-Report-Spam: http://spam.gmane.org/gmane.comp.sysutils.supervision.general:814 --=-=-= 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 --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iQEVAwUAQou/3TyfXseeoEz2AQo8cgf+NlgVToEY7q19aPRO60bmKi39XP3YONPx T8fi63jtol9i7v3nvd5sFtw5TdXfb3tyiQyD/S/lCvl9DO3oU5NNNaqi+iJ8TkDh HCmzUmRoeeXEVxmaJPSckp9AwTS8ePVZy9K0hHEjVzDSD5k+zTiqmmA1XiUl20xL VrRD9XfAkkzk9auOMLvsYhTlr8qy1ki45yW79c69kp53xzrJRAa6K6ydS053eah6 lS9es45p49xHY11hYQCxOHNEeSknj0teSMl4tHauaHZ1ShqP39V8n6iuEOoF8XPp wSQsz1XV5Xy9z9Sw1uTNRdNRP22Fl/zkqOn9l9e4htm7FHYlDARSuQ== =j67y -----END PGP SIGNATURE----- --=-=-=--