Hello,
Resolved.
Thanks for your support Jeff.
We successfully patched our Apache.
We will as well plan an upgrade later this year.
Best,
Nourrédine
On Wed, Aug 21, 2013 at 5:27 PM, Nourredine Rouibah <
nourredine.roui...@gmail.com> wrote:
> Hi,
>
> Just a confirmation:
>
> - I did apply *o
Hi,
Just a confirmation:
- I did apply *only* this patch:
https://issues.apache.org/bugzilla/show_bug.cgi?id=47645#c13 described in
the link in comment #13.
I did not apply the other ones mentionned in comments #5 and #11
https://issues.apache.org/bugzilla/show_bug.cgi?id=47645#c11
https://issu
On Tue, Aug 20, 2013 at 10:40 AM, Nourredine Rouibah <
nourredine.roui...@gmail.com> wrote:
> Hi,
>
> After rebuilding Apache with the patch on port.c, is it correct to just
> replace libapr-1.so.0.3.7
> in the running apache installation ? That would speed up the fix.
>
You have to
* make a ba
Hi,
After rebuilding Apache with the patch on port.c, is it correct to just
replace libapr-1.so.0.3.7
in the running apache installation ? That would speed up the fix.
thanks,
/Nourrédine.
On Tue, Aug 20, 2013 at 2:51 PM, Jeff Trawick wrote:
> On Tue, Aug 20, 2013 at 8:00 AM, Nourredine Rou
On Tue, Aug 20, 2013 at 8:00 AM, Nourredine Rouibah <
nourredine.roui...@gmail.com> wrote:
> Hi,
>
> After doing some search I suspect our problems to be related with this
> issue : https://issues.apache.org/bugzilla/show_bug.cgi?id=47645
>
> I say that because the problem started to happen as soo
