summaryrefslogtreecommitdiffstats
path: root/www/squid26/pkg-descr
diff options
context:
space:
mode:
authoradrian <adrian@FreeBSD.org>2001-03-27 12:28:47 +0000
committeradrian <adrian@FreeBSD.org>2001-03-27 12:28:47 +0000
commit3ca2480a29d24957776816eb442841b3ed5c718c (patch)
tree230051f19e722703ee78f04c82878f06a4fd922a /www/squid26/pkg-descr
parentbf27a3f66a942e0a43c6de636c0d99d8802f7f8e (diff)
downloadFreeBSD-ports-3ca2480a29d24957776816eb442841b3ed5c718c.zip
FreeBSD-ports-3ca2480a29d24957776816eb442841b3ed5c718c.tar.gz
PR: 26059
Update the squid-2.4 port to actually _be_ squid-2.4 . Phew. This port builds, installs, packages, pkg_delete's cleanly. I'm going to run it through some more linting and tidying up before I'm completely done with it. Differences from squid22/squid23 : * install-pinger isn't built. I'll tackle this later, possibly by creating a squid user/group. I don't like having suid binaries installed, even more so when 99% of the users of this port won't even enable ICMP pinging. * I've enabled the lru and heap replacement policies. LRU is used by default, the beauty here is that the user can choose one or the other without needing a recompile. * I've enabled ufs (sync), diskd (async) and null (no caching, only proxying). This again lets users choose what they want without needing a recompile. The default is still a 100mb cache in /usr/local/squid/cache/ running ufs. I would change it to diskd but if the user hasn't tweaked their sysV shm/msg parameters sufficiently they'll just be puzzled when squid gives mysterious sysV errors (and if they load it up enough to have UFS become an issue, they'd be better off reading the squid FAQ anyhow..)
Diffstat (limited to 'www/squid26/pkg-descr')
-rw-r--r--www/squid26/pkg-descr4
1 files changed, 2 insertions, 2 deletions
diff --git a/www/squid26/pkg-descr b/www/squid26/pkg-descr
index 646e01d..a030d6c 100644
--- a/www/squid26/pkg-descr
+++ b/www/squid26/pkg-descr
@@ -11,7 +11,7 @@ continued development of the cache where Harvest finished.
FreeBSD PORTER'S NOTES. To this moment, Squid is not well documented.
But you aren't lost in space: there is a mailing list,
-<squid-users@nlanr.net>, where you will find some support and help.
+<squid-users@squid-cache.org>, where you will find some support and help.
We also _strongly_ suggest you to examine Web pages noted above.
-WWW: http://squid.nlanr.net/Squid/
+WWW: http://www.squid-cache.org/
OpenPOWER on IntegriCloud