| Main Archive Page > Month Archives > syslog-ng-users archives |
Re: [syslog-ng] segfault in 3.4 alpha1
From: Peter Czanik <czanik_at_nospam>Date: Mon Mar 19 2012 - 14:07:34 GMT
To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu>
On 03/14/2012 09:55 AM, Balazs Scheidler wrote:
> .
> I don't think so, the one found by Peter is probably related to the new
> file-perm specifying code, which may not have been properly used in the
> afsocket module.
>
> Now as I was second guessing it, I've found the culprit, it is fixed
> here:
>
> commit daded120cefa7217dac0b1a5d9a870a7fa7fc51d
> Author: Balazs Scheidler<bazsi@balabit.hu>
> Date: Wed Mar 14 09:54:35 2012 +0100
Just verified, the segfault is gone and alpha1 starts now also on
FreeBSD. I'll check the json part of the port next.
Bye,
-- Peter Czanik (CzP)<czanik@balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/ ______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq