On Sun, 18 Apr 2004, Marc MERLIN wrote:
> Typically, that's because of a bug in Exim (or one of the libs/calls it
> uses), that causes it to go out of bounds.
> With PAX, it gets killed before it has a chance to get a SEGV from the kernel
>
> Either way, PAX is not responsible for this as far as I can tell, and
> chpax won't help you. I'm almost certain that you're just hitting an exim crash
Okay, thanks for the info. From what I was able to google, someone had
recommended turning off perl to avoid these errors, so I was wondering if
the perl support tried to execute from data segments or something like
that.
If it was just PAX catching either a crash or an intentional buffer
overflow, then that's fine, I was just curious.
Thanks
-Scott
--
Scott Call Router Geek, ATGi, home of $6.95 Prime Rib
I make the world a better place, I boycott Wal-Mart
VoIP incoming: +1 360-382-1814
