X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
X-Yahoo-Newman-Property:	ymail-3
X-Yahoo-Newman-Id:	709477 DOT 19815 DOT bm AT omp114 DOT mail DOT ac4 DOT yahoo DOT com
X-YMail-OSG:	sWdGBF8VM1l__HPede.1XKwnl2D46m0wmVaD93pRqj5PW6EFqp9auZcuQvRqLwjZD.NQacXRD63695mD_Dqewf0WRwPd0ZuAPyHaUVkN9w--
X-Mailer:	YahooMailWebService/0.7.218.2
Date:	Thu, 21 Aug 2008 21:14:11 -0700 (PDT)
From:	Grav Yam <gravyam AT yahoo DOT com>
Reply-To:	gravyam AT yahoo DOT com
Subject:	Having trouble with syslog-ng using lots of CPU
To:	cygwin AT cygwin DOT com
MIME-Version:	1.0
Message-ID:	<514701.28085.qm@web59706.mail.ac4.yahoo.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Hi -

Even when nothing else is happening, and nothing is being logged, the syslog-ng service is consistently using up 50% of my cpu under a win2k host.

I've looked though the mailing list archives and also googled around a lot looking for a solution, but no one else seems to really have this problem. Has anyone there heard of anything like it?

Some info:

$ uname -a
CYGWIN_NT-5.0 jamro 1.5.25(0.156/4/2) 2008-03-05 19:27 i686 Cygwin

$ cygcheck -c syslog-ng
Cygwin Package Information
Package              Version        Status
syslog-ng            2.0.7.1-1      OK


And here is my syslog-ng.conf:

$ cat /etc/syslog-ng.conf
options {
  keep_hostname(yes);
  chain_hostnames(no);
  owner("gravy");
  group("web");
  perm(0664);
  sync(0);
};

source applications {
  internal();
};

destination messages {
  file("/var/log/messages");
};

log {
  source(applications);
  destination(messages);
};

source s_teabag_port { tcp(port(30303)); };
destination teabag_loghost { tcp("192.168.10.25" port(30303)); };
log { source(s_teabag_port); destination(teabag_loghost); };

source s_teapot_port { tcp(port(30304)); };
destination teapot_loghost { tcp("192.168.10.25" port(30304)); };
log { source(s_teapot_port); destination(teapot_loghost); };



Let me know if any other info can be useful. Thanks for any help!

Grav



      


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -