The problem is, if (s)he is using the official packages, he will get the
updates of the mainline channel, thus differing more and more from the
stable channel which is supposed to be cheaper on features but with usable
ones.

My 2 cents,
---
*B. R.*

On Mon, Jun 6, 2016 at 12:05 PM, Maxim Konovalov <maxim@nginx.com> wrote:

> On 6/6/16 1:00 PM, A. Schulze wrote:
> >
> > Hello,
> >
> > I'm using horde and observe similar errors since some weeks.
> > Unsure if the same problem would be the reason.
> >
> > Maxim Konovalov:
> >> It was fixed in 1.11.0 two weeks ago.
> >
> > I found one patch 'preread_buffer.patch" attachtd to
> > https://trac.nginx.org/nginx/ticket/959
> > That patch looks not trivial (to me)
> > Would it be possible to publish a version for nginx-1.10.1, too
> >
> > I would try if that solve the errors I observe.
> >
> Why don't you just try 1.11.1?
>
> The code difference between it and 1.10.1 (already released a week
> ago) is marginal.
>
> --
> Maxim Konovalov
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx