RE: [squid-users] Changing cache location

Since I asked the question orginally here was my resolution.
1. Edited squid.conf to reflect the new location on another partition for the cache.
2. Stopped squid (could have stopped it first)
3. ./squid -z to create the new cache.
4. restarted squid
5. I downloaded a huge file and checked the new partiton and it grew in space taken up so I knew I was successful.
6. I didn't try ./squid -z while it was actually running.
7. It is caching just fine.

Gary

---------- Original Message ----------------------------------
From: "Lightfoot.Michael" <Lightfoot.Michael@comcare.gov.au>
Date: Wed, 12 Mar 2003 10:01:26 +1100

>>
>> ext2 does not have block fragments, and this problem does not occur
>> there.
>>
>Hmmm. The only cache I have ever run on Linux is on a Debian system and
>had similar symptoms as the UFS problem on Solaris - the filesystem
>wasn't full (AFAIR), but the cache ran out of space. This was nearly
>two years ago so perhaps my memory of the problem is faulty.
>
>So what causes problems on ext2 as I observed?
>
>> Solaris can be tuned to mostly get rid of the problem by tuning the
>> filesystem to optimize for space. See the Squid FAQ.
>>
>Done that. I have my UFS cache directories mostly under control. I was
>inexpertly illustrating.
>
>
>
>
>Michael Lightfoot
>Unix Consultant
>ISG Host Systems
>Comcare
>+61 2 62750680
>Apologies for the rubbish that follows...
>------------------------------------------------------------------------
>NOTICE: This e-mail message and attachments may contain confidential
>information. If you are not the intended recipient you should not use or
>disclose any information in the message or attachments. If received in
>error, please notify the sender by return email immediately. Comcare
>does not waive any confidentiality or privilege.
>
>
>
Received on Tue Mar 11 2003 - 16:33:42 MST