Anybody else see this under high load or when mozilla/phoenix walks into the
wrong kind of website?

the log floods with:

_XSERVTransSocketUNIXAccept: accept() failed

in a tight loop, and the browser goes unresponsive until killed. Then the
logflood dies.

I hesitate to call this a bug. I suspect its like uninitialized fixup logs, its
the system telling you the truth here: something is very unhappy.

Equally, it stinks of code not reading an feof() condition right on a network
binding and re-re-re-re-reading <i am not here> as the empty return.

current as for 1 week ago, current xsrc as well.

cheers
	-George
-- 
George Michaelson       |  APNIC
Email: ggm@apnic.net    |  PO Box 2131 Milton QLD 4064
Phone: +61 7 3367 0490  |  Australia
  Fax: +61 7 3367 0482  |  http://www.apnic.net