From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/817 Path: news.gmane.org!not-for-mail From: Dean Hall Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: svlogd as a heavy-duty logger Date: Thu, 19 May 2005 08:30:44 -0400 Message-ID: References: <428ACC2E.5090000@gmail.com> <877jhwjhuq.fsf@kosh.bigo.ensc.de> Reply-To: Dean Hall NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1116505948 26894 80.91.229.2 (19 May 2005 12:32:28 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 19 May 2005 12:32:28 +0000 (UTC) Original-X-From: supervision-return-1053-gcsg-supervision=m.gmane.org@list.skarnet.org Thu May 19 14:32:21 2005 Return-path: Original-Received: from antah.skarnet.org ([212.85.147.14]) by ciao.gmane.org with smtp (Exim 4.43) id 1DYk9y-0002n6-Lb for gcsg-supervision@gmane.org; Thu, 19 May 2005 14:29:55 +0200 Original-Received: (qmail 30476 invoked by uid 76); 19 May 2005 12:31:09 -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 30470 invoked from network); 19 May 2005 12:31:08 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=mO1qHWtMrqxQmVgYYWe+yhx4sskjef6aHQYcyzfVrsXUQrQZdrK4VH93nuZucyxvlEuOYyFXCiYWvu7FNM9cocKPZyac+yfgHlm3uU97Vz3e5mQuV4rLpXr5T+kcQC5r3HeFPaeygI5IM+xU6FwKQJ0f9Vq2E1AVshhTHmnD+S4= Original-To: supervision@list.skarnet.org In-Reply-To: <877jhwjhuq.fsf@kosh.bigo.ensc.de> Content-Disposition: inline Xref: news.gmane.org gmane.comp.sysutils.supervision.general:817 X-Report-Spam: http://spam.gmane.org/gmane.comp.sysutils.supervision.general:817 Enrico, > > Has anyone load-tested svlogd, or does anyone have experience with > > svlogd's behavior under a heavy load? >=20 > 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 suppor= t > basic functions: >=20 > * 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 I don't need to encrypt anything. Also, we'd probably only use one svlogd process as a child of socklog, which would then, I assume, spawn an svlogd child for each log directory. Maybe someone can correct me here. > * logrotation is very unflexible; low-volume logs will be transmitted ver= y > seldom and svlogd does not support a way to rotate them periodically. Y= ou > will need external programs started e.g. by cronjobs which send SIGALRM > to svlogd. But this will have bad sideeffects as it rotates all logfile= s > but not only the low-volume ones. I'm not sure what you mean. You can use the "s" option in the config file to specify a size at which to rotate, and, as Gerrit pointed out, you can now use the "t" option to specify the age in seconds at which to rotate. So if you want small logs rotated or not, you can do it. None of this is an issue for me anyway. > At the end, I switched to syslog-ng. It offers more flexibility and is > more lightweighted. I'm not sure what kind of flexibility syslog-ng has. AFAIK, svlogd (+ socklog) can do everything (plus some) that syslog-ng can. Like I said, we're using syslog-ng, and it's not good enough for us. Dean