tis 2008-12-02 klockan 09:40 -0500 skrev Rick Chisholm: > I'm having a recurring issue with squid 2.7STABLE5 on FreeBSD 6.3 - part > of the problem is that I cannot pinpoint the cause. Often (though not > always) when squid -k reconfigure is run squid goes a bit haywire and > maxes out one core and becomes unresponsive to connections. Please attach gdb to the process and print out a stack backtrace to figure out what it's doing. cat /usr/local/squid/logs/squid.pid gdb /usr/local/squid/sbin/squid <pidofsquid> gdb> backtrace then file a bugreport with the output. <pidofsquid> is the number returned by the command above.. Trying "squid -k debug" to get more detailed output in cache.log is also worthwhile, but begin with the backtrace. Regards Henrik
