I haven't tried it yet, and I'm in the middle of the Polymix-4 run so
can't test it, but while digging through the logs to see the "reasons
we've crashed today", I realized a problem with the ramdisk--swap.state
grows faster than I normally rotate (quite a lot faster during a fill)
leading it to overrun the disk and crash Squid. The good news is that
every crash over the past week has a good explanation, and it was never
due to Squid bugs, unless you count fragility in the face of full disks
a bug.
Is it safe to route it to /dev/null or even hack Squid to disable it
entirely? As far as I know it's only used on restarts to speed the
building of the in-memory cache state...so can I kill it or should I
just remove it hourly and squid -k rotate?
Thanks!
-- Joe Cooper <joe@swelltech.com> http://www.swelltech.com Web Caching Appliances and SupportReceived on Fri Nov 09 2001 - 21:33:08 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:14:37 MST