The problem is still active in Apache 1.3.6 (current version). Still appears that the clients (or servers) are disconnecting during the transfer leaving the tmp files in place. Note - this may be more of a server disconnect problem. I recently changed CacheForceCompletion 100 which should remove tmp files for client disconnect. Have not reviewed code in detail to determine what happens in client disconnect instances.
Problem remains "non critical" since cache cleanup removes these files once they expire. ted keller On 5 May 1999 [EMAIL PROTECTED] wrote: > [In order for any reply to be added to the PR database, ] > [you need to include <[EMAIL PROTECTED]> in the Cc line ] > [and leave the subject line UNCHANGED. This is not done] > [automatically because of the potential for mail loops. ] > [If you do not include this Cc, your reply may be ig- ] > [nored unless you are responding to an explicit request ] > [from a developer. ] > [Reply only with text; DO NOT SEND ATTACHMENTS! ] > > > Synopsis: Apache does not always unlink tmp files in apache cache area > > State-Changed-From-To: open-feedback > State-Changed-By: coar > State-Changed-When: Wed May 5 13:27:37 PDT 1999 > State-Changed-Why: > [This is a standard response.] > This Apache problem report has not been updated recently. > Please reply to this message if you have any additional > information about this issue, or if you have answers to > any questions that have been posed to you. If there are > no outstanding questions, please consider this a request > to try to reproduce the problem with the latest software > release, if one has been made since last contact. If we > don't hear from you, this report will be closed. > If you have information to add, BE SURE to reply to this > message and include the [EMAIL PROTECTED] address so it > will be attached to the problem report! >
