On 15/07/11 20:59, Linda Walsh wrote:
Amos Jeffries wrote:
As documented this bundle had a lot of deep I/O and communication
architectural changes. Instability is/was expected.
Most of the bugs you hit are now resolved in the daily update bundle.
If you need a relatively stable 3.2 release please use 3.2.0.8.
---
I thought 3.2.0.9 was latest stable in that series...my bad.
No, that whole series is beta still. 3.2.1 will be the first stable. We
are ~25 major bugs and one more big feature merge away from that.
Squid-3.2 IPC is (wrongly) hard-coded to use PREFIX/var/run instead of
the system local state dir. We are in progress fixing that now.
----
It doesn't use what's from 'configure'?
Suse's config process uses a val of prefix=/usr, so
it would have been trying to use '/usr/var/run', which would
be a problem... ;-)
Yes. That. http://bugs.squid-cache.org/show_bug.cgi?id=3267
I could have resorted to backups, but wanted to work forward.
Am working through several follow probs from my server distro
upgrade (lots of consequential problems in refixing config stuff...)..
So when I get back to a stable 'network', Maybe I'll try finding the
3.2.HEAD (am presuming that's what it would be called...)....
When you are ready. It is at
http://www.squid-cache.org/Versions/v3/3.2/ under the texts about "Daily
auto generated..."
or via rsync://squid-cache.org/source/squid-3.2 which is updated daily
with the bug fixes.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.14
Beta testers wanted for 3.2.0.9
