[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: cache problems State-Changed-From-To: open-feedback State-Changed-By: martin State-Changed-When: Wed Apr 28 06:25:00 PDT 1999 State-Changed-Why: It seems that two different errors are mixed in this PR. a) [error] (17)File exists: proxy: error linking cache file This error can occur under normal situations when two requests to the same URL happen in parallel (two proxy children). A better concept of "shared memory interprocess request table" between proxy children might resolve this (not anytime soon...). b) [error] (16)Device busy: Hmmm. What can apache do about that? It seems to be an error in your OS. All the proxy does is call unlink(name). If Solaris can't handle that, then.... :-( Also, I don't see how apache can be involved in the inability to handle large disks, other than the fact that one GC must have terminated before the next one starts. Did you observe any core dumps? Beware, there might be no log message about it (GC is detached!). Try to trigger a GC by touching 0101010170 cache/.time and watch the background process. Recently in 1.3.7-dev, we had a core dump candidate. Try to report any findings. Thank you.
