On 02.02.17 15:54, Tory M Blue wrote:
> I'm not seeing any issue but the error is rampant at this point
>
> 2017/02/02 10:58:59 kid1| /cache/07/49/003749FE
> 2017/02/02 10:59:00 kid1| DiskThreadsDiskFile::openDone: (2) No such
file or
> directory
> 2017/02/02 10:59:00 kid1|
On Thu, Feb 2, 2017 at 3:51 PM, Amos Jeffries wrote:
> On 3/02/2017 7:56 a.m., tmb...@gmail.com wrote:
> > asnani_satish wrote
> >> This happens when size specified in cache_mem >= cache_dir
> >> Example:
> >> cache_dir aufs /var/spool/squid 1000 32 512
> >>implies 1000
On 3/02/2017 7:56 a.m., tmb...@gmail.com wrote:
> asnani_satish wrote
>> This happens when size specified in cache_mem >= cache_dir
>> Example:
>> cache_dir aufs /var/spool/squid 1000 32 512
>>implies 1000 MB physical disk space allotted for cache in specified
>> directory
>> cache_mem 900
lol
mostly of this ar wen vary changed lol
wen they work on vary as it should be then most of those msg will go away
not 100% but most of them
im not going into detail but its the vary in header
--
View this message in context:
asnani_satish wrote
> This happens when size specified in cache_mem >= cache_dir
> Example:
> cache_dir aufs /var/spool/squid 1000 32 512
>implies 1000 MB physical disk space allotted for cache in specified
> directory
> cache_mem 900 MB
>cache size to be used by squid which must be less
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/26/2014 02:22 PM, HackXBack wrote:
Hello squid , after using 3.5.0.4 on fresh debian system i see many
errors in cache.log
Hey There,
(leaving aside these errors)
As a part of a cache proxy integration I am generally recommending to
do it in
Nothing to worry about. The files were removed by some outside
software and were not found. Squid will manage the error and carry on.
On Fri, Dec 26, 2014 at 1:22 PM, HackXBack hack.b...@hotmail.com wrote:
Hello squid ,
after using 3.5.0.4 on fresh debian system
i see many errors in cache.log