* Add a PORTREVISION line, like I guess it should have had the last
time I updated this port
* Update the port to use squid-2.3STABLE5 . This code base fixes the
recent possible security problems with squid23 (twas not a root exploit,
it was a possible DoS-other-hosts bug if the default config had been
modified to enable a specific form of http acceleration)
* Remove the patches - they're not needed with 2.3-STABLE5
options `start' and `stop' now (unless I have forgotten any). This allows
us to call the scripts from /etc/rc.shutdown with the correct option.
The (42 or so) ports that already DTRT before are unchanged.
Synopsis:
"If you fill up your squid cache, CPU will go to 100% but the cache will not be
cleaned up."
PR: 18920
Submitted by: Mike Harding <mvh@ix.netcom.com>
Obtained from: http://www.squid-cache.org/Versions/v2/2.3/bugs/
- the distributed patches got regenerated to have the correct paths
- disable optimization because of gcc bugs (as recommended by squid folks)
- list a few new --enable/--disable options
Squid 2.0 is the-version-formerly-known-as-1.2.
v2.0 has NOVM-like functionality internally, so there's no seperate
NOVM version. v1.1.* is no longer officially supported.
Note: the b14 -> b15 change will loose your cache unless you take
the steps on http://squid.nlanr.net/ to recover it.
Read the Changelog for details, this is a fairly large update.
Major changes:
- the URL and SHA cache key methods are gone, MD5 is the only option.
- the swap.state system has been redesigned as a transaction log for
much faster restarts and crash recovery.
- SIZE on ftp binary transfers.
- Lots of bug fixes and code cleanups.
From the web page; http://squid.nlanr.net/Squid/1.2.beta/
WARNING, with beta12 we are starting to stuff object metadata into
the beginning of objects on disk. With beta13 we have changed the
"swap.state" file format to binary instead of text. When you run this
version for the first time you WILL LOSE YOUR CACHE!
The previous warning still stands:
This is BETA software. Do not run this on your production systems.
Logfile formats are subject (and likely) to change at any time without
warning.
Index: like posix says, rather than going into dummy mode. The distributed
patches are generated with standard cvs and don't have ache's hack (which
doesn't work when new files are added anyway).
