Yup, same behaviour at our site, Solaris 2.6, SUN Ultra 1, 386 Mbyte RAM, 4 GB Cache Dir, same Squid version 2.4stable1.
I have cronjobs running like this:
# Rotate log-files of squid and restart process
0 4 * * * /opt/squid/bin/squid -k rotate > /dev/null 2>&1
10 4 * * * /etc/init.d/proxy.server stop > /dev/null 2>&1
20 4 * * * /etc/init.d/proxy.server start > /dev/null 2>&1
...works fine.
> -----Ursprüngliche Nachricht-----
> Von: Mike Diggins [mailto:diggins@mcmail.cis.mcmaster.ca]
> Gesendet: Freitag, 3. August 2001 14:56
> An: squid-users@squid-cache.org
> Betreff: [squid-users] Squid getting too big?
>
>
> I'm concerned about how quickly Squid is growing in size. The cache has
> been up for only a few weeks. Up until yesterday it was growing slowly and
> was up to 230 MB, last night it was at 440 MB and this morning it's at 514
> MB according to TOP.
>
> The platform is Solaris 8 running on a Sun Ultra 10 with 1 GB RAM and two
> 16 GB cache dirs (separate disks). The cache is still only 40% full.
> Should I be concerned?
>
> CPU states: 89.6% idle, 4.4% user, 5.2% kernel, 0.8% iowait, 0.0% swap
> Memory: 1024M real, 259M free, 583M swap in use, 2167M swap free
>
> PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND
> 22469 root 1 53 0 515M 514M sleep 450:39 3.72% squid
>
> -Mike
Received on Fri Aug 03 2001 - 07:13:27 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:01:27 MST