[syslog-ng] Syslog-ng-2.05 Segmentation Fault

[Daniel Szmandiuk]

Evan,

That's the sort of answer I was after.

Daniel 

-----Original Message-----
From: syslog-ng-bounces at lists.balabit.hu
[mailto:syslog-ng-bounces at lists.balabit.hu] On Behalf Of Evan Rempel
Sent: Friday, 9 November 2007 10:10 AM
To: Syslog-ng users' and developers' mailing list
Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault

These options are documented in the "./configure --help" which is the
script provided with the source tree for compilation, but since you are
already reading this...

--enable-static-linking makes the compiled binary independent from
anything else on the system. The intent is to provide an application
that will not get "broken" when shared libraries are updated sometime in
the future.
There are a couple of caveates about this, but I'm not going to get into
that here.

--enable-tcp-wrapper=no makes the resulting syslog-ng NOT check the
/etc/hosts.allow and /etc/hosts.deny files for remote connection
authorization.

Evan.

Daniel Szmandiuk wrote:
> Evan,
> 
> Please excuse by ignorance but what do the following options do?
> 
> --enable-static-linking
> --enable-tcp-wrapper=no
> 
> Thanks in advance,
> 
> Daniel
>  
> 
> -----Original Message-----
> From: syslog-ng-bounces at lists.balabit.hu
> [mailto:syslog-ng-bounces at lists.balabit.hu] On Behalf Of Evan Rempel
> Sent: Friday, 9 November 2007 9:31 AM
> To: Syslog-ng users' and developers' mailing list
> Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault
> 
> I compiled from source.
> 
> env PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure 
> --enable-static-linking --enable-tcp-wrapper=no
> 
> glib2-2.4.7-1
> glib2-devel-2.4.7-1
> gcc-c++-3.4.6-8
> gcc-3.4.6-8
> 
> Evan.
> 
> Daniel Szmandiuk wrote:
>> Scott / Evan
>>
>> Did you compile from source or did you use the supplied binaries?
>>
>> Daniel
>>  
>>
>> -----Original Message-----
>> From: syslog-ng-bounces at lists.balabit.hu
>> [mailto:syslog-ng-bounces at lists.balabit.hu] On Behalf Of ScottO
>> Sent: Friday, 9 November 2007 5:59 AM
>> To: Syslog-ng users' and developers' mailing list
>> Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault
>>
>> Ditto.
>>
>> I also am running it on 64bit hosts (CentOS 4 & Fedora Core 3), 
>> albeit
> 
>> only for a couple days now (2.0.5 that is) - without any segfault'ing

>> issues.
>>
>> Evan Rempel wrote:
>>> Yes, I am using syslog-ng 2.0.5 on redhat4 64bit and not having any 
>>> problem with crashing etc.
>>>
>>> Anything I can help with I will try and do.
>>>
>>>
>>> Evan.
>>>
>>> Balazs Scheidler wrote:
>>>> Hm.. the same has been reported on a mips64 system. This must be a
>>>> 64
>>>> bit related issue, then. I'll try to get a 64 compile environment.
>>>>
>>>> Anyone else who uses syslog-ng 2.0.x on 64 bit systems?
>>>>
>>>> On Thu, 2007-11-08 at 23:34 +1100, Daniel Szmandiuk wrote:
>>>>> Here's the backtrace:
>>>>> GNU gdb Red Hat Linux (6.5-16.el5rh) Copyright (C) 2006 Free 
>>>>> Software Foundation, Inc.
>>>>> GDB is free software, covered by the GNU General Public License, 
>>>>> and you are welcome to change it and/or distribute copies of it 
>>>>> under certain conditions.
>>>>> Type "show copying" to see the conditions.
>>>>> There is absolutely no warranty for GDB.  Type "show warranty" for

>>>>> details.
>>>>> This GDB was configured as "x86_64-redhat-linux-gnu"...Using host 
>>>>> libthread_db library "/lib64/libthread_db.so.1".
>> _______________________________________________
_______________________________________________
syslog-ng maillist  -  syslog-ng at lists.balabit.hu
https://lists.balabit.hu/mailman/listinfo/syslog-ng
Frequently asked questions at http://www.campin.net/syslog-ng/faq.html


This email and any attachments transmitted with it are confidential and may contain legally privileged information.  If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it.  If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments.

It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system.  IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email.

For information about our privacy policy, visit the IMC Communications website at www.imc.net.au

This email has been checked by IMC's SMTP gateway.
-&-