Yes, the tcpdump data backs this up as well.
I also see
[Tue May 01 16:10:19 2001] [error] (32)Broken pipe: core_output_filter: writing data to the networkrning: junk pointer, too high to make sense.
httpd in free(): warning: junk pointer, too high to make sense.
httpd in free(): warning: junk pointer, too high to make sense.
httpd in free(): warning: junk pointer, too high to make sense.
httpd in free(): warning: junk pointer, too high to make sense.
httpd in free(): warning: junk pointer, too high to make sense.
httpd in free(): warning: junk pointer, too high to make sense.
pretty clear it's a memory problem. It's a small one, because it takes a looong time to run out far enough to casue the problem.
Chuck
On Wednesday, May 2, 2001, at 08:46 AM, Graham Leggett wrote:
Chuck Murcko wrote:
One interesting thing I noticed in my logs yesterday:
[Mon Apr 30 03:00:39 2001] [error] [client 172.16.86.108] client denied by server configuration: proxy:http://a772.g.akamai.net/7/772/51/bf8b48bb5bd500/www.apple.com/macosx/ images/action_fonts.gif, referer: http://www.apple.com/macosx/
This is definitely "memory getting stomped on" material, my most hated style of bug. Sigh.
Chuck Murcko Topsail Group http://www.topsail.org/
