> Am 06.06.2017 um 10:45 schrieb Plüm, Rüdiger, Vodafone Group > <[email protected]>: > > > >> -----Ursprüngliche Nachricht----- >> Von: Stefan Eissing [mailto:[email protected]] >> Gesendet: Dienstag, 6. Juni 2017 10:40 >> An: [email protected] >> Betreff: Re: The drive for 2.4.26 >> >> Proposed the patch as fix, since we did not see the behaviour pop up >> again over the last days at Steffen's system. >> >> I assume the RTC is in place now. > > My personal opinion: Only after 2.4.26 is released. So from my personal point > of view you can go ahead backporting. > Others may see this differently.
I shall use the time our US friends are still slumbering on to back port the change, taking your statement as an excuse. :-P -Stefan > > Regards > > Rüdiger > >> >> -Stefan >> >>> Am 06.06.2017 um 09:26 schrieb Stefan Eissing >> <[email protected]>: >>> >>> I made a patch on Friday evening for Steffen's system where the >> behaviour happens. Hope to hear back from him today. >>> >>> -Stefan >>> >>>> Am 06.06.2017 um 03:12 schrieb Eric Covener <[email protected]>: >>>> >>>> On Tue, May 30, 2017 at 9:12 AM, Stefan Eissing >>>> <[email protected]> wrote: >>>>> I have one report of a CPU busy loop that seems to only happen on >> the last 3 changes in mod_http2. Steffen is currently testing if a >> feature disable solves the problem and thus points to the cause. I hope >> to hear from him tomorrow sometime during the day if that addresses the >> issue or not. >>>>> >>>>> Otherwise I am hesitant to make any more changes from my side and >> hope we can go forward with a release. >>>> >>>> >>>> Anything on this? >>>> >>>> -- >>>> Eric Covener >>>> [email protected] >>> >
