diff options
| author | Adrian Chadd <adrian@FreeBSD.org> | 2001-03-27 12:28:47 +0000 |
|---|---|---|
| committer | Adrian Chadd <adrian@FreeBSD.org> | 2001-03-27 12:28:47 +0000 |
| commit | 88dd211266913d0df8c20d25df96c11041e4f94c (patch) | |
| tree | edff426bdf7c55288de3d1aa4ac38e64c1c2c382 /security/kmap | |
| parent | aba319a01e6dcfb3fd15e9d20f6f1b1eb40b519e (diff) | |
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 'security/kmap')
0 files changed, 0 insertions, 0 deletions
