Re: libpcap causing segmentation fault

[Moshe Matitya <Moshe.Matitya () xconnect net>]

On Tuesday, February 14, 2012 9:17 PM, Michael Richardson wrote:
> That's a significant jump in functionality. 
> I don't think 2.4 had any memory mapped functionality  at all.
>
> If 2.6.18 has any (redhat likes to backport all sorts of things), the
> question becomes... does it work?  2.6.18 is 5 years old.
>
> My suggestion is to turn off (in the source code), any of the mmap
> functionality, or at least printf() what is being used.   I would also
> wonder if you are doing technology renewal, why you are stopping at
> Centos 5, rather than 6 (or higher?) with a linux 3.0 kernel...

Our IT department is rather conservative about upgrades.  They won't upgrade to a new major version before a subsequent 
bug-fix minor version is released, and there was a long span of time between the releases of CentOS 6.0 and 6.1, during 
which time they standardized our servers on an earlier version.  At this point, they aren't prepared to switch, so I 
have no choice but to deal with 5.6.

Could you give me any pointers as to what I need to do in the code to turn off mmap functionality?

Thanks,

Moshe

-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.