I would say given the severity of this issue (of making the server
*unusable* with regular use), we should have atleast some fix, or to
disable squid (which it is by default?) while better/practical approaches
are discussed.
Also, we do have monit. Maybe there is a way to get it to monitor squid
c
You don't say why a separate partition is impractical.
The Squid intent from antiquity was that the filesystem be separate,
which in those days was only practical and performant with separate
partition or disk, with a filesystem tuned for many small files.
To use a separate filesystem yet avoid s
I don't think it is practical to have a separate partition and while
http://wiki.squid-cache.org/SquidFaq/ConfiguringSquid#What_.27.27cache_dir.27.27_size_should_I_use.3F
talks about a separate partition, it and other docs make it clear that the
entire partition should not and need not be used
I don't think it is practical to have a separate partition and while
http://wiki.squid-cache.org/SquidFaq/ConfiguringSquid#What_.27.27cache_dir.27.27_size_should_I_use.3F
talks about a separate partition, it and other docs make it clear that the
entire partition should not and need not be used
I think this is serious enough to warrant atleast a doc note to have the
squid cache in a different partition as it makes the machine completely
unusable otherwise. I don't think it is maybe the best idea to have it in
library (but rather a separate partition).
Or, as you say, a cron job - but in
This happened in Rwanda, but the settings said 20M.
Sent from my Samsung Galaxy smartphone.
Original message
From: Anish Mangal Date:
5/5/16 9:20 PM (GMT-08:00) To: xsce-devel
, server-devel
Subject: [XSCE] Has anyone else seen squid swap.state bloat?
Yesterday, an in
