> On May 12, 2018, at 10:23 AM, Mark Blackman <m...@exonetric.com> wrote:
> I think you will find it difficult to re-work effectively unless you can 
> identify representative test cases possibly including a segfault.
> For me the most important characteristics of the fix were (a) to more 
> accurately identify genuine virtual host changes (rather than simple line 
> number shifts) that might invalidate balancer state and at least in some 
> cases, to pick up existing SHMs left-over from the last httpd start. 

Thx... I still think that all the recent changes to the module has made it more 
fragile than it was before... But whatever 

Reply via email to