[syslog-ng] [Bug 43] syslog-ng 2.1.4 consumes all CPU when processing "source file"

[bugzilla at bugzilla.balabit.com]

https://bugzilla.balabit.com/show_bug.cgi?id=43





--- Comment #3 from Denis Laplante <denis.laplante at ubc.ca>  2009-04-30 20:47:10 ---
(In reply to comment #2)
> can you try 3.0 if it fixes your problem? 
Yes, 3.0.1 on Solaris-8 fixes this problem.  

Looking at "truss" output, version 2.0.10 used "poll" to sleep, while malfunctioning version 2.1.4 used "alarm".
>5.2506 read(3, 0x00087898, 8192) = 0
>5.2508 alarm(0)                  = 10
>5.2509 alarm(10)                 = 0
>5.2511 read(3, 0x00087898, 8192) = 0
>5.2513 alarm(0)                  = 10
>5.2514 alarm(10)                 = 0
>5.2516 read(3, 0x00087898, 8192) = 0

I will read MacPorts.org docs for creating and testing a new "portfile" for version 3.0.1 on MacOsX.

Because of difficulties in killing syslog-ng-2.1.4, here is my procedure to stop runaway processes after 2 seconds:
$ bash
$ ulimit -t 2
$ syslog-ng-3.0.1/src/syslog-ng -f ./syslog-ng.local.3.conf --pidfile ${PWD}/syslog-ng-test.pid -d -F

How do I suppress pidfile and/or control socket? 
> Error opening control socket, bind() failed; error='Permission denied (13)', socket='/local/var/run/syslog-ng.ctl'


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.