I am not sure if I should start another thread with this - my apologies for
bumping it . . .
but in the last post I was looking to see if these 4 steps was a sensible
method of telling the proxy to only cache certain sites:
*
STEP 1/4
*
acl noproxy dstdomain .com .net .org etc, etc.
*
On 1/09/2013 4:14 a.m., HillTopsGM wrote:
I am not sure if I should start another thread with this - my apologies for
bumping it . . .
but in the last post I was looking to see if these 4 steps was a sensible
method of telling the proxy to only cache certain sites:
*
STEP 1/4
*
acl noproxy
If I under stand you then, just *remove* the '*always_direct allow noproxy*'
and the steps I have posted should work?
does the order in which these appear in the squid.conf file:
cache allow windowsupdate
cache deny noproxy
. . . matter?
I don't believe they should as they are defined more
On 1/09/2013 4:34 a.m., HillTopsGM wrote:
If I under stand you then, just *remove* the '*always_direct allow noproxy*'
and the steps I have posted should work?
Yes.
does the order in which these appear in the squid.conf file:
cache allow windowsupdate
cache deny noproxy
. . . matter?
In connection with my last post, I also had this question:
Let's say that with my 4GB of RAM I decided to create a total cache
storage
area that was 650GB; obviously the index would be much larger than could
be
stored in RAM.
If my primary purpose was to 'archive' my windows updates, I'd
The rule-of-thumb is 15MB *per GB of cache size*.
Thanks Amos - that's the rule of thumb I was looking for.
Somewhere along the way I thought I saw 10MB per GB of Cache but it was
vague.
I was also given a piece of advice to maybe create multiple directories of
no more than 100 GB per.
I
In connection with my last post, I also had this question:
Let's say that with my 4GB of RAM I decided to create a total cache storage
area that was 650GB; obviously the index would be much larger than could be
stored in RAM.
If my primary purpose was to 'archive' my windows updates, I'd expect
On 25/08/2013 11:20 a.m., HillTopsGM wrote:
In connection with my last post, I also had this question:
Let's say that with my 4GB of RAM I decided to create a total cache storage
area that was 650GB; obviously the index would be much larger than could be
stored in RAM.
If my primary purpose
Hallo, HillTopsGM,
Du meintest am 22.08.13:
*Question 2:* Seeing how this is significantly larger that the
default 100 MB should I consider increasing the size of the 16 256
in the above sample code?
That depends!
I know many squid installations in schools, with about 200 ... 500
clients
On 23/08/2013 5:27 p.m., HillTopsGM wrote:
Thanks for the Reply Amos.
As per my original post, can anyone comment on the original 2 questions?
*Question 1:* If I wanted to dedicate 3 GB of the Ram to the index, would
that mean that I should set my cache_dir to 3072?
cache_dir ufs
Thanks for the Reply Amos.
As per my original post, can anyone comment on the original 2 questions?
*Question 1:* If I wanted to dedicate 3 GB of the Ram to the index, would
that mean that I should set my cache_dir to 3072?
cache_dir ufs /usr/local/squid/var/cache 3072 16 256
*Question 2:*
That's really interesting!
I'll look into it a little closer, however, I already have the hardware, and
there is the potential to use the system for other program updates within
the network.
I thought that I'd /start/ by focusing on something like Windows Updates,
with the idea that I could
On 22/08/2013 5:59 a.m., HillTopsGM wrote:
That's really interesting!
I'll look into it a little closer, however, I already have the hardware, and
there is the potential to use the system for other program updates within
the network.
I thought that I'd /start/ by focusing on something like
13 matches
Mail list logo
