On Aug 25, 2004, at 1:40 AM, Elsen Marc wrote:




greetings

i have squid running as a transparent proxy with squidguard as a
content filter. I recently increased the filter list size and my
machine is choking when i rotate the logs.

i have a cron job execute squid -k rotate at night. the CPU
pegs out at
100% and it takes for ever for squidguard to process the blacklists.
without intervention the machine will choke itself to death
and restart.

with intervention i have been able to flush my IPFW redirect, load
squid, wait 20 minutes until the CPU is done processing the the
blacklist then add the redirect statements back in. the whole process
takes about 30 minutes start to finish.

is there a cleaner way to rotate? the 30 min down time seems too long.

running squid-2.5 Stable6 & squidguard 1.2


Make sure to use the pre-formatted db files when using SquidGuard otherwise SQ
has to create this db format in memory when the squidguard processes are restarted,
which also happens as a result of 'squid -k rotate'. This can take considerable
overhead and delay. Create db files for squid at all times and when blacklists are
updated using :


            % squidGuard -C all


OMG,.. thank you for removing my head from backside. I totally forgot about that process.
Thanks


-j

-----------------------------------
jeff donovan
basd network operations
(610) 807 5571 x41
AIM  xtdonovan



Reply via email to