On Wed, May 31, 2006 at 09:43:45PM +0200, Willy Tarreau wrote:
> On Wed, May 31, 2006 at 09:50:38PM +0200, Manfred Spraul wrote:
> > Marcelo Tosatti wrote:
> >
> > >Since v2.4.33 should be out RSN, my opinion is that applying the
> > >one-liner to fix the bringup problem for now is more prudent..
On Wed, May 31, 2006 at 09:50:38PM +0200, Manfred Spraul wrote:
> Marcelo Tosatti wrote:
>
> >Since v2.4.33 should be out RSN, my opinion is that applying the
> >one-liner to fix the bringup problem for now is more prudent..
> >
> >
> >
> It's attached. Untested, but it should work. Just the rel
Marcelo Tosatti wrote:
Since v2.4.33 should be out RSN, my opinion is that applying the one-liner
to fix the bringup problem for now is more prudent..
It's attached. Untested, but it should work. Just the relevant hunk from
the 0.42 patch.
But I would disagree with waiting for 2.3.34 for
On Wed, May 31, 2006 at 07:54:38AM +0200, Willy Tarreau wrote:
> On Wed, May 31, 2006 at 07:50:32AM +0200, Manfred Spraul wrote:
> > Hi Willy,
> >
> > Willy Tarreau wrote:
> >
> > >I started from the latest backport you sent in september (0.42) and
> > >incrementally applied 2.6 updates. I stoppe
On Wed, May 31, 2006 at 07:50:32AM +0200, Manfred Spraul wrote:
> Hi Willy,
>
> Willy Tarreau wrote:
>
> >I started from the latest backport you sent in september (0.42) and
> >incrementally applied 2.6 updates. I stopped at 0.50 which provides
> >VLAN support, because after this one, there are s
Hi Willy,
Willy Tarreau wrote:
I started from the latest backport you sent in september (0.42) and
incrementally applied 2.6 updates. I stopped at 0.50 which provides
VLAN support, because after this one, there are some 2.4-incompatible
changes (64bit consistent memory allocation for rings, and
