On Sun, Apr 18, 2004 at 05:38:28PM -0700, Scott Call wrote:
> 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.
Well, there's an easy way to find out
chpax -p /usr/sbin/exim
chpax -s /usr/sbin/exim
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | Finger marc_f@??? for PGP key
