wessels [Tue, 16 May 2000 13:05:50 +0000 (13:05 +0000)]
DW:
- Synced HEAD with SQUID_2_3 branch as of SQUID_2_3_STABLE3. Can't
say it was fun. I wouldn't be surprised if some conflicts got
resolved incorrectly.
wessels [Fri, 12 May 2000 09:43:00 +0000 (09:43 +0000)]
DW:
- The removal of storeClientListSearch broke validation requests.
A clientHttpRequest (http) can register itself with two StoreEntrys.
One is the old entry that needs validation, and the other is
the one to hold the validation response from the origin server.
With the new scheme, clientHttpRequest needs and 'old_sc' to go
with 'old_entry'.
wessels [Fri, 12 May 2000 09:32:24 +0000 (09:32 +0000)]
DW:
- When diskd got MODIO'ified, this important bit got dropped for some
reason. If we don't drain the queue sometimes in MsgSend, its
quite possible to run out of shared memory buffers. Probably event
more important, we don't want to have too many messages outstanding
without processing some replies back from the diskd daemons.
wessels [Fri, 12 May 2000 04:20:57 +0000 (04:20 +0000)]
DW:
- Jens-S reports internal DNS code happily resolves ".foo.com" while
external DNS gives an error. This patch makes internal DNS return
a "the domain name does not exist" error message.
wessels [Thu, 11 May 2000 09:05:23 +0000 (09:05 +0000)]
DW:
Benno Rice (benno@netizen.com.au) reports "two instances where
read handlers were treating their fd_table read data as a pointer
to an int and attempting to increment it, even though NULL was
passed, or somesuch"
adrian [Sun, 7 May 2000 22:18:19 +0000 (22:18 +0000)]
Killing the abuse of storeClientListSearch() in the code. Now the
client list per memObject is a dlink_list rather than a single linked
list. storeClientListAdd() returns a store_client * which is then
used whenever storeClientCopy()/storeUnregister() is called.
adrian [Sat, 6 May 2000 22:44:26 +0000 (22:44 +0000)]
brought over from modio - storeExpiredReferenceAge() isn't applicable
in the current storage layout. It will result in soon to be expired
objects (LRU) entering the digest, but there isn't a hook in the
current code to check this cleanly, so the code has been commented out.
adrian [Wed, 3 May 2000 23:15:38 +0000 (23:15 +0000)]
MODIO_1 commit. This change (including documentation) implements a more
modular storage directory system, which leaves object replacement and IO
up to the storage modules.
There is a lot of repeated code in the FS modules and some tidying up
is in the pipeline.
The documentation for this new API is in doc/Programming-Guide/prog-guide.sgml .
hno [Wed, 3 May 2000 03:35:24 +0000 (03:35 +0000)]
hno squid-2.3.STABLE1.strict_authenticate_ip_ttl.patch [variant there of]
Squid-2.3.STABLE1: strict authenticate_ip_ttl option
Changed authenticate_ip_ttl to have an strict option, enforcing that
the user comes from one IP address only.
Changes from the patch: Added another squid.conf directive for enabling
this rather than overloading the authenticate_ip_ttl option with negative
values..
hno [Wed, 3 May 2000 03:21:05 +0000 (03:21 +0000)]
hno squid-2.3.STABLE1.http_reply_null_character.patch
Squid-2.3.STABLE1: Handle NULL characters in the server reply headers
Squid failed to detect the end of the servers HTTP headers if the server
wrongly responds with headers containing a NULL character. This could
cause abnormal amount of used cache_mem during the request. (the server
in question was mp3 streaming, virtuallu unlimited in size)
hno [Wed, 3 May 2000 02:58:29 +0000 (02:58 +0000)]
hno squid-2.3.DEVEL3.squid.conf_template_update-4.patch
Squid-2.3.DEVEL3: Major update of squid.conf template generation
A major update on how squid.conf is generated from cf.data.pre and
some related changes.
* Default lines are generated from the compiled default settings (less
duplication in cf.data.pre)
* Non-enabled functions gets a note telling that the directive isn't enabled
and what configure option (or defined) that is required to enable it.
hno [Wed, 3 May 2000 02:41:22 +0000 (02:41 +0000)]
hno squid-2.3.DEVEL3.ftp_all_messages.patch
Squid-2.3.DEVEL3: Show FTP server messages
Show all FTP server messages in generated error pages or top level
directory listing. Main purpose is to make sure all information is
available when a login is denied due to to many users or a closed
mirror.
hno [Wed, 3 May 2000 02:31:44 +0000 (02:31 +0000)]
hno squid-2.3.DEVEL3.round_robin_clear_counter.patch
Squid-2.3.DEVEL3: Reset "round-robin" counters every 5 minutes
Reset "round-robin" peer selection counters every 5 minutes to speed up
recovery when a dead peer has come on line again ("round-robin" is
implemented by "least-frequently-used", which without this patch gets
stronly biased to the previously dead peer).
hno [Wed, 3 May 2000 02:18:21 +0000 (02:18 +0000)]
hno squid-2.3.DEVEL2.ipcache_reload.patch
Squid-2.3.DEVEL2: Purge ipcache on reload/PURGE
Purge negatively cached ipcache entries on reload to allow end users to
quickly purge sporious errors, and have the PURGE method also purge
ipcache to allow the cache administrator to manually purge important
entries on DNS updates.
hno [Wed, 3 May 2000 02:07:37 +0000 (02:07 +0000)]
hno squid-2.3.DEVEL2.rebuild_release.patch
Squid-2.3.DEVEL2: Release unused store entries during rebuild
Squid locked all "released" store entries in memory during the rebuild
procedure, even such entries not needed in the "LateRelease" procedure.
Also, during a dirty rebuild a lot of store entries got locked up which
never was queued for "LateRelease", causing a huge memory leak.
hno [Wed, 3 May 2000 01:53:52 +0000 (01:53 +0000)]
hno squid-2.3.STABLE1.no_cache_full_acl_check.patch
Squid-2.3.STABLE1: Make no_cache a full-blown aclNBCheck
no_cache was a fast ACL check, which serverely limits which acl types
that can be reliably used. This patch extends it to a full blown
aclNBCheck which allows all of the ACL types to be used like in
http_access.
hno [Wed, 3 May 2000 01:43:30 +0000 (01:43 +0000)]
hno squid-2.3.DEVEL2.cache_swap_log_name-2.patch
Squid-2.3.DEVEL2: cache_swap_log name based on cache_dir name
%s can now be used in cache_swap_log to build a log file name based on
the cache_dir name instead of numbering the files according to their
corresponding cache_dir location in squid.conf. This is very useful if
you'd like to be able to add or remove cache directories while using
cache_swap_log to have the index files stored outside the cache
directories.
hno [Wed, 3 May 2000 01:40:12 +0000 (01:40 +0000)]
hno squid-2.2.STABLE4.aio_cond_segfault-2.patch
Squid-2.2.STABLE4: Async-IO segfaults if AIO_PROPER_MUTEX isn't set
Async-IO on Linux segfaults in condition variables if given high load
and AIO_PROPER_MUTEX isn't set. This was seen on a SMP Alpha Linux
2.2.10-ac12 box. I knew there was a reason why I made the
AIO_PROPER_MUTEX code a long time ago..
[an incorrect version of this simple patch was already committed]
hno [Wed, 3 May 2000 01:35:23 +0000 (01:35 +0000)]
hno squid-2.2.STABLE5.log_ip_on_direct.patch with additions
Squid-2.2.STABLE5: Log destination IP on DIRECT
This patch logs the destination IP as part of the hierarchy tag in
access.log when going direct. This has been requested by a number of
people from accounting reasons, and logging the hostname is mostly
redundant as it is part of the URL as well.
Additions: Can be rewerted to the old behaviour by turning log_ip_on_direct off
hno [Wed, 3 May 2000 01:21:59 +0000 (01:21 +0000)]
hno squid-2.3.DEVEL2.stat_ufs_fs.patch
Squid-2.3.DEVEL2: Show usable filesystem space in cachemgr, not raw
Change cachemgr Store Directory Stats to show space available to Squid
rather than raw filesystem space (some space are available to root only)
Also extend the support for this on Linux.
hno [Wed, 3 May 2000 00:55:10 +0000 (00:55 +0000)]
hno squid-2.2.STABLE2.delay_pools_initial_level_overflow.patch
Squid-2.2.STABLE2: delay pools, large initial level
It was a bit to easy to get a integer overflow when using delay pools for
limiting daily download. Changes the initial calculation to use floating
point math, allowing a initial pool size of up to 2^31-1.
allow-miss cache peer option to disable the use of "only-if-cached" on
requests to siblings. This can be useful in some peering arrangements
where icp_hit_stale is enabled.
hno [Wed, 3 May 2000 00:49:26 +0000 (00:49 +0000)]
hno squid-2.2.STABLE2.to_large_objects-2.patch
Squid-2.2.STABLE2: Don't swap out objects > maximum_object_size
Don't start swapping out objects with a known size larger than
maximum_object_size. Previously Squid would swap out these objects and
mark it as private once maximum_object_size was hit.
This is an attempt to fix the dynamic ICP timeout selection when one is
peering with remote parents and have some close-by siblings with a much
lower ICP rtt. This is done by preferring to calculate the ICP timeout
based on parents only (based on siblings if there is no alive parents)
New squid.conf directive: nonhierachical_direct. This controls if
requests Squid classifies as non-hierarchical (matches
hierarchy_stoplist or non-cachable request type) should go direct if
possible, or if parents should be used on such requests. Also improved
parent selection for never_direct to try to selects all available parents
to increase the likelyhood that there is at least one alive parent where
the request can be forwarded.
DW:
- storeSwapout() has a recently-added bug that causes huge amounts
of memory to get tied up for some pending requests. Observed what
seemed to be a "Range" request where store_client->copy_offset
was larger than MemObject->inmem_hi. That is, the server side
didn't yet get the data that the client wants. In this case, the
whole object was being stored in memory.
The cause was the recent change so that more objects can be
cached in memory, rather than always freeing up to the lowest
reader offset.
The fix (hack?) is to check the case when lowest offset is larger
than inmem_hi. It also requires changing storeLowestMemReaderOffset
so that the initial "low_offset" is inmem_hi+1.
DW:
- Disabling a mysterious block at the beginning of httpRequestFree
that causes incomplete transfers to be logged with status code
"000." There seems to be no bad side effects from taking it out.
DW:
- Fix possible memory access bug. Before the change we would always
copy 4096 bytes from 'headers' to 'buf'. Not only was it wasteful,
but it accessed uninitialized memory.
wessels [Thu, 9 Mar 2000 11:50:13 +0000 (11:50 +0000)]
DW:
- storeMaintainSwapSpace was breaking out of the scan loop if the
current space was below the HIGH water mark, but the event is
rescheduled at a small interval when space is near the high water
mark. Changed the check to use the low water mark instead.
wessels [Mon, 6 Mar 2000 23:24:56 +0000 (23:24 +0000)]
DW:
- We're passing -1 swapfile number to storeDirDiskFull becuse the
swapfile number got reset earlier. Need to pass the 'bad' swapfile
number instead..
wessels [Tue, 1 Feb 2000 12:52:15 +0000 (12:52 +0000)]
DW:
- This fixes an ugly and probably old bug with hot objects. Previously,
storeSwapOut was too aggressive in freeing lower parts of in-memory
objects. It would free up to how ever much was sent to the client,
or how much had been saved to disk, whichever was lower. When the
object response is complete, it is saved in memory only if mem->inmem_lo
was equal to zero. Thus, many objects which could potentially be
held in memory wouldn't be, because the lower part had been freed
in storeSwapOut.
This change doesn't free the lower part until the hi-lo gap is
at least DISK_PAGE_SIZE (8192 bytes). This means that in-memory
hot objects should mostly be 8kb or less. This change makes a
very significant improvement in memory hit ratio.
wessels [Tue, 1 Feb 2000 12:45:33 +0000 (12:45 +0000)]
DW:
- Changed validation process to scan 500 (instead of 50) objects
per call. This should be fine because validation does not much
more than set the ENTRY_VALIDATED flag for each object.
wessels [Tue, 1 Feb 2000 12:43:02 +0000 (12:43 +0000)]
DW:
- Changed storeGetMemSpace so that it doesn't immediately exit
if the store is in rebuilding phase. Purging memory objects
should be a "light" activity, so there should be no performance
penalty. If we don't purge memory objects during the rebuild
phase, then memory usage grows without bounds until rebuilding
is complete. At high workloads this can cause malloc to fail.