[squid-users] Impressions about 3.2.0.7
I would like to thank squid team for the good work on 3.2.0.7. I went from 3.2.0.1 to 3.2.0.7 straight to development and faced no issues. Runs reliably since 2 weeks. 1. Irritating 0 HTTP Response Code on CONNECT to peers fixed. 2. Equally irritating CD_SIBLING_HIT and all CD_ are replaced with ANY_OLD_PARENT (we have cache digest disabled on compile) 3. %oa ported from 2.7 and works fine (%la). 4. --disable-ipv6 does not work. We had to modify configure to include #define USE_IPV6 0 to remove ipv6. 5. -fPIE does not work as always (standard on RHEL). Thank you again. Jenny
Re: [squid-users] Impressions about 3.2.0.7
On 05/05/11 19:58, Jenny Lee wrote: I would like to thank squid team for the good work on 3.2.0.7. I went from 3.2.0.1 to 3.2.0.7 straight to development and faced no issues. Runs reliably since 2 weeks. 1. Irritating 0 HTTP Response Code on CONNECT to peers fixed. 2. Equally irritating CD_SIBLING_HIT and all CD_ are replaced with ANY_OLD_PARENT (we have cache digest disabled on compile) 3. %oa ported from 2.7 and works fine (%la). 4. --disable-ipv6 does not work. We had to modify configure to include #define USE_IPV6 0 to remove ipv6. 5. -fPIE does not work as always (standard on RHEL). Thank you again. Jenny Is that all a list of fixed? or are 4 5 still problems? Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.12 Beta testers wanted for 3.2.0.7 and 3.1.12.1
RE: [squid-users] Impressions about 3.2.0.7
4. --disable-ipv6 does not work. We had to modify configure to include #define USE_IPV6 0 to remove ipv6. 5. -fPIE does not work as always (standard on RHEL). Is that all a list of fixed? or are 4 5 still problems? Hello Amos, #4 and #5 are are still problems. #5 is bug 2996. -fPIE does not work on RHEL5 or RHEL6 with 3.2's (I don't know about earlier versions). Jenny
