From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LlrT1-000745-6m for garchives@archives.gentoo.org; Mon, 23 Mar 2009 21:13:55 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 76126E0320; Mon, 23 Mar 2009 21:13:40 +0000 (UTC) Received: from mail-qy0-f108.google.com (mail-qy0-f108.google.com [209.85.221.108]) by pigeon.gentoo.org (Postfix) with ESMTP id 57364E0320 for ; Mon, 23 Mar 2009 21:13:40 +0000 (UTC) Received: by qyk6 with SMTP id 6so2690100qyk.32 for ; Mon, 23 Mar 2009 14:13:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=oL2btOiHOLe3pSBZacOR7K5Oy43QdYHeTEj97zL4hKY=; b=hMBAShLpDk4DrwMLyB7wV4/Th6mZclu2c3i/vf6w7i3q2TF9slptZO6DB/fjq6y/B3 LZtfMKijvzMs4qug1+1ZhCt/YW7p+76mqbXibZDiQ8QI0RJ3pwcJneT5SN06u5cehI/B 6m0mHZs6ofifrQo44DdY2qsYnDnBt6Ne+CbRA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=pLu6Wilzy83COu1CZjPh3Uzdah7l8EPv+PEkRhgGNwCeANR6inT71KhX/ibmNMAuHR ROc4b1mkOXvv0vplJSH0ZMlQSgN7GCHkEAaPxw8o3I6EsP5rAyrFlYSW4FpRs88wA+oJ IgtJ6miid1VtI0XRcQ/KqRFnzwUZ2YbgEsJws= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Sender: paul.hartman@gmail.com Received: by 10.224.3.2 with SMTP id 2mr9580202qal.367.1237842820111; Mon, 23 Mar 2009 14:13:40 -0700 (PDT) In-Reply-To: <49C7E7C4.1020701@shic.co.uk> References: <49C7ACEB.9050307@shic.co.uk> <49C7E293.9040705@shic.co.uk> <49C7E3A9.3030300@shic.co.uk> <49C7E7C4.1020701@shic.co.uk> Date: Mon, 23 Mar 2009 16:13:40 -0500 X-Google-Sender-Auth: a089b4d3646146f3 Message-ID: <58965d8a0903231413hb59bfbdmb2fc56f51e19c275@mail.gmail.com> Subject: Re: [gentoo-user] Syslog-ng using a spectacular amount of CPU time... (I'm using sshguard) From: Paul Hartman To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 23bc6f40-b78e-4243-8b76-78b8fd9d01e4 X-Archives-Hash: 4a188bc24dd5052686621cc74a63bbfc On Mon, Mar 23, 2009 at 2:49 PM, Steve wrote: > Steve wrote: >> >> Do others get this behaviour - is this a bug in syslog-ng? > > Sorry for the multiple posts... a slight error on my part. The sshguard > process wasn't running - a /bin/sh process trying to spawn it was running > (there was no link from /usr/local... to the binary) and when the binary > failed to execute - syslog-ng got itself into a tiz. Everything seems to > work fine when I correct the path to the program. > > Problem solved - but, I guess, this is a flaw in syslog-ng... I'd have hoped > it would generate an error message rather than behave as it did. I had a possibly similar problem a while back with syslog-ng going crazy when a certain daemon would crash (in my case it filled up the log wit about 60 gigabytes of the same thing repeated over and over, in addition to using massive CPU%). I switched to metalog and haven't had any problems since.