[syslog-ng] [Bug 255] segmentation faults often

[bugzilla at bugzilla.balabit.com]

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





--- Comment #8 from Evan Rempel <erempel at uvic.ca>  2013-10-21 01:21:44 ---
more than 30 million log messages and there is no sign of a memory leak or a segfault.

Time    USER    PID     PPID    NI      PRI     %CPU    VSZ     ELAPSED         TIME            COMMAND
103101  root    12307   19898   0       19      13.5    694896  00:06:11        00:00:50        /usr/local/sbin/syslog-ng
104601  root    12307   19898   0       19      12.8    695132  00:21:11        00:02:43        /usr/local/sbin/syslog-ng
110101  root    12307   19898   0       19      12.7    705376  00:36:11        00:04:36        /usr/local/sbin/syslog-ng
111601  root    12307   19898   0       19      12.6    695104  00:51:11        00:06:28        /usr/local/sbin/syslog-ng
113101  root    12307   19898   0       19      12.8    705348  01:06:11        00:08:28        /usr/local/sbin/syslog-ng
114601  root    12307   19898   0       19      12.9    695104  01:21:11        00:10:30        /usr/local/sbin/syslog-ng
120101  root    12307   19898   0       19      13.0    695120  01:36:11        00:12:30        /usr/local/sbin/syslog-ng
121601  root    12307   19898   0       19      13.1    695168  01:51:11        00:14:35        /usr/local/sbin/syslog-ng
123101  root    12307   19898   0       19      13.1    695168  02:06:11        00:16:38        /usr/local/sbin/syslog-ng

So I think we are safe on the memory leak worry, and I'm fairly confident that this has
addressed the segfault.

As I said earlier, I'll wait for the load of a weekday of business before I completely sign off on this,
but it is looking really good.


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