Balazs Scheidler <bazsi@balabit.hu> wrote:
I have found two problems which are the possible cause of the crashes reported on this list. expect a new release soon if the fixes below prove to be effective.
I am very happy to report that 1.5.23+libol-0.3.5 are running just fine in my environment. Before I discovered 1.5.23 was available I had already tested 1.5.21+the sources.c patch, and that worked for me as well.
Thanks very much for taking the time to stomp this bug out of existence!
cool, and thanks for testing the fix. if syslog-ng 1.5.23 proves to be stable, I'll release 1.6.0
Could you - not specifically you, rather the list - please test the configure.in changes as well on different platforms?
I've tested it on Debian GNU/Linux, and Solaris 8 (Linux on x86, Solaris on Sparc).
Now that you mention it... on Solaris 2.6 I had to use the attached patch for syslog-ng to build. On Solaris 8 I had to invoke configure this way in order to *really* disable res_init: /bin/env blb_cv_c_res_init=no ./configure --sysconfdir=/etc Otherwise, I ended up with this (notice there are two res_init() checks, and one succeeds): [...] checking for I_CONSLOG... yes checking for O_LARGEFILE... yes checking for res_init... yes checking for working alloca.h... yes checking for alloca... yes checking for vprintf... yes checking for door_create in -ldoor... yes checking for select... yes checking for snprintf... yes checking for vsnprintf... yes checking for strerror... yes checking for inet_aton... no checking for strncpy... yes checking for getutent... yes checking for res_init... no checking for getopt_long... no checking for strcasecmp... yes checking for strptime... yes [...] Thanks.