I think, I found the cause myself: The cache_dir directive had settings from an earlier Squid proxy server, which had a bigger cache disk. (I C&Ped them when I set up the current proxy server). It was: The current Squid server has a cache disk of 20GB and according to the description of the cache_dir directive http://www.squid-cache.org/Doc/config/cache_dir/ it should be at maximum 20% smaller than the available disk space: My question regarding different process owners remains: Why runs the parent squid process as root and the child as user proxy? Is that normal? Is it best practice? Should I chmod or chown cache directory? -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-3-doesn-t-overwrite-replace-cached-objects-tp4661911p4661921.html Sent from the Squid - Users mailing list archive at Nabble.com.
